run-llama/create-llama
1
0
Fork 0
mirror of https://github.com/run-llama/create-llama.git synced 2026-07-16 03:04:21 -04:00
Code Issues 39 Packages Projects Releases 10 Wiki Activity

[PR #698] [MERGED] Fix broken devcontainer due to deleted repo #694

New Issue
Closed
opened 2026-02-15 20:15:53 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 20:15:53 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/run-llama/create-llama/pull/698
Author: @andyfowler
Created: 6/29/2025
Status: ✅ Merged
Merged: 6/29/2025
Merged by: @marcusschiesser

Base: main ← Head: fix-broken-devcontainers-tools

📝 Commits (2)

  • dac3441 fix broken links to devcontainers features
  • 976bb88 Create warm-actors-obey.md

📊 Changes

2 files changed (+7 additions, -2 deletions)

View changed files

➕ .changeset/warm-actors-obey.md (+5 -0)
📝 packages/create-llama/templates/devcontainer.json (+2 -2)

📄 Description

The devcontainers-contrib repo / registry has been removed (and is at risk of supply chain squatting?). So, running a newly-created create-llama project in VSCode fails to create the dev container with the errors:

Could not resolve Feature manifest for 'ghcr.io/devcontainers-contrib/features/turborepo-npm:1'.  If necessary, provide registry credentials with 'docker login <registry>'.
Could not resolve Feature 'ghcr.io/devcontainers-contrib/features/turborepo-npm:1'.  Ensure the Feature is published and accessible from your current environment.

Somebody is currently hosting a warning at the old registry https://github.com/devcontainers-contrib/features.

This PR replaces the devcontainer tools with equivalents, found via the official tools list at https://containers.dev/features

Summary by CodeRabbit

  • Chores
    • Updated development container configuration to use new sources and versions for TypeScript and Turborepo features.
    • Fixed development container setup issue caused by a deleted repository.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/create-llama/pull/698 **Author:** [@andyfowler](https://github.com/andyfowler) **Created:** 6/29/2025 **Status:** ✅ Merged **Merged:** 6/29/2025 **Merged by:** [@marcusschiesser](https://github.com/marcusschiesser) **Base:** `main` ← **Head:** `fix-broken-devcontainers-tools` --- ### 📝 Commits (2) - [`dac3441`](https://github.com/run-llama/create-llama/commit/dac344171cb886e680f42cbd799006431b498f86) fix broken links to devcontainers features - [`976bb88`](https://github.com/run-llama/create-llama/commit/976bb8881cbbb6b368a026a69d4f0610061593e8) Create warm-actors-obey.md ### 📊 Changes **2 files changed** (+7 additions, -2 deletions) <details> <summary>View changed files</summary> ➕ `.changeset/warm-actors-obey.md` (+5 -0) 📝 `packages/create-llama/templates/devcontainer.json` (+2 -2) </details> ### 📄 Description The `devcontainers-contrib` repo / registry has been removed (and is at risk of supply chain squatting?). So, running a newly-created `create-llama` project in VSCode fails to create the dev container with the errors: ``` Could not resolve Feature manifest for 'ghcr.io/devcontainers-contrib/features/turborepo-npm:1'. If necessary, provide registry credentials with 'docker login <registry>'. Could not resolve Feature 'ghcr.io/devcontainers-contrib/features/turborepo-npm:1'. Ensure the Feature is published and accessible from your current environment. ``` Somebody is [currently hosting a warning](https://github.com/devcontainers-contrib/features?tab=readme-ov-file) at the old registry https://github.com/devcontainers-contrib/features. This PR replaces the devcontainer tools with equivalents, found via the official tools list at https://containers.dev/features <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated development container configuration to use new sources and versions for TypeScript and Turborepo features. * Fixed development container setup issue caused by a deleted repository. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 20:15:53 -05:00
yindo closed this issue 2026-02-15 20:15:53 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/create-llama#694
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?