Repository navigation
refactor!: rename the scaffolded backend folder to cdk-blocks - #1630
Open
VarshithaPamisetty wants to merge 1 commit into
Open
VarshithaPamisetty wants to merge 1 commit into
VarshithaPamisetty wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: f92dae5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 27 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
VarshithaPamisetty
force-pushed
the
fix/cdk-blocks-folder-rename
branch
2 times, most recently
from
November 18, 2026 17:08
a548c5d to
0177e23
Compare
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
temporarily deployed
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Inactive
VarshithaPamisetty
temporarily deployed
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Inactive
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
temporarily deployed
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Inactive
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:13 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:14 — with
GitHub Actions
Error
VarshithaPamisetty
temporarily deployed
to
e2e
November 18, 2026 17:14 — with
GitHub Actions
Inactive
VarshithaPamisetty
had a problem deploying
to
agent-bench
November 18, 2026 17:17 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
agent-bench
November 18, 2026 17:17 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
agent-bench
November 18, 2026 17:17 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
agent-bench
November 18, 2026 17:17 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
agent-bench
November 18, 2026 17:17 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
agent-bench
November 18, 2026 17:17 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
agent-bench
November 18, 2026 17:17 — with
GitHub Actions
Error
VarshithaPamisetty
temporarily deployed
to
e2e
November 18, 2026 17:36 — with
GitHub Actions
Inactive
VarshithaPamisetty
temporarily deployed
to
e2e
November 18, 2026 17:36 — with
GitHub Actions
Inactive
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:36 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:36 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:36 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:36 — with
GitHub Actions
Error
VarshithaPamisetty
temporarily deployed
to
e2e
November 18, 2026 17:36 — with
GitHub Actions
Inactive
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 17:37 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
agent-bench
November 18, 2026 17:39 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
agent-bench
November 18, 2026 17:39 — with
GitHub Actions
Error
VarshithaPamisetty
temporarily deployed
to
agent-bench
November 18, 2026 17:39 — with
GitHub Actions
Inactive
VarshithaPamisetty
had a problem deploying
to
agent-bench
November 18, 2026 17:39 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
agent-bench
November 18, 2026 17:39 — with
GitHub Actions
Error
VarshithaPamisetty
temporarily deployed
to
agent-bench
November 18, 2026 17:39 — with
GitHub Actions
Inactive
VarshithaPamisetty
temporarily deployed
to
agent-bench
November 18, 2026 17:39 — with
GitHub Actions
Inactive
VarshithaPamisetty
had a problem deploying
to
agent-bench
November 18, 2026 17:39 — with
GitHub Actions
Error
VarshithaPamisetty
temporarily deployed
to
agent-bench
November 18, 2026 17:39 — with
GitHub Actions
Inactive
VarshithaPamisetty
had a problem deploying
to
agent-bench
November 18, 2026 17:39 — with
GitHub Actions
Error
VarshithaPamisetty
force-pushed
the
fix/cdk-blocks-folder-rename
branch
3 times, most recently
from
November 18, 2026 18:00
2e0dc13 to
8c96d0a
Compare
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 18:05 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 18:05 — with
GitHub Actions
Error
VarshithaPamisetty
had a problem deploying
to
e2e
November 18, 2026 18:07 — with
GitHub Actions
Error
This was referenced Nov 18, 2026
xyos
previously approved these changes
Nov 19, 2026
This branch is being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The scaffolded backend folder is named
aws-blocks/, but the product is nowcdk-blocks. Bareblockswas ruled out as a third name, so the folder, the package it declares, and the specifier the frontend imports all have to move together.Changes
cdk-blocks/across 33 directories (222 file renames): the 14create-blocks-apptemplates, 17 test apps, and the Swift and Kotlin examples."name"(18 manifests), the parent's"workspaces"entry (27 manifests, including 13 path-form entries in the root), and everyfrom 'aws-blocks'import (173 occurrences in 104 files). Renaming the directory alone leaves imports resolving by package name, so a green suite would not prove the rename landed.LEGACY_BLOCKS_BACKEND_DIRincore/src/common/constants.tsand afindLegacyProjectRootpath that onlymigrateopts into.migratereads a pre-rename app, so it keeps detectingaws-blocks/; every other command detects the current name.index.test.tspins both constants so a future bulk rename cannot sweep the legacy one up with the rest.cdk-blocksin CLI help and generated scripts to\bcdk-blocks(?!/). They guard the removed bin, and the folder now shares its name, so acdk-blocks/path must not trip them.Breaking / maintainer review: an existing app renames the directory, its
"workspaces"entry, the"name"in itscdk-blocks/package.json, and everyfrom 'aws-blocks'import. There is no dual-name support and no compatibility shim; preview customers are asked to migrate. Deliberately unchanged: the reserved URL namespace (/aws-blocks/api,/aws-blocks/auth/*,/aws-blocks/dashboard, 1727 occurrences) so deployed API Gateway routes and OAuth callback URLs already registered with an identity provider keep working; the@aws-blocks/*npm scope; theaws-blocksuser-agent token, which the warehouse filters on;aws-blocks:stub-idpand the versionedaws-blocks:key-fingerprint:v1separator; releasedCHANGELOG.mdand.changeset/entries; the 114 GitHub URLs, since the repository keeps its name; and the npmkeywordsentry, which is a separate open question.Validation
sedwas used.npm run build: exit 0, 0 TypeScript errors.origin/mainate1e484465fails 15:core1,create-blocks-app14 (alltemplate "X" enables @aws-blocks/bb-data:encryptStorageByDefault).blocks0 = 0,core1 = 1,create-blocks-app14 = 14,bb-auth0 = 0,admin-ui0 = 0,hosting0 = 0. Delta: 0 new failures. Built and run withTMPDIRon a non-symlinked path, sincemkdtempandrealpathdiffer on macOS.blocksfailsstops npm run dev and its frontend on a SIGTERM to its process groupabout one run in three, and passes on re-run. It is a signal-timing test and does not reference either folder name.admin-uiduplicate, the GitHub URLs and the history files are untouched. It was mutation-tested in 8 states: all-done passes, and directory-stale, name-stale, workspaces-stale, import-stale, history-edited, github-edited and route-edited each fail on their own.e1e484465, which landed feat(blocks)!: run app tasks through package scripts instead of cdk-blocks #1610 and added 535 newaws-blocksreferences. The change was re-derived through the same classification pipeline on that base rather than hand-resolving 27 conflicts, so one rule set covers the whole diff.npm run test:e2e:localand the puppeteer suites. This worktree installs withPUPPETEER_SKIP_DOWNLOAD=1becausechrome-headless-shellwill not install here.The
*-aws-blocksworkspace package names in the test apps stay as they are. npm requires a unique name per workspace across the monorepo, so only one backend can be calledcdk-blocks(test-apps/comprehensiveholds that slot). Each of those apps imports the name it declares, or aliasescdk-blocksto its ownclient.js, so nothing resolves by the old folder name.