refactor: move npm package into javascript/ - #208
Merged
Merged
Conversation
tvdeyen
force-pushed
the
refactor/monorepo-package-separation
branch
from
September 1, 2026 06:16
57e4527 to
734007a
Compare
tvdeyen
force-pushed
the
refactor/monorepo-package-separation
branch
from
September 1, 2026 10:08
53c738f to
665083d
Compare
tvdeyen
changed the title
5 tasks
tvdeyen
marked this pull request as ready for review
September 1, 2026 10:20
tvdeyen
added a commit
that referenced
this pull request
Sep 1, 2026
Stage 2 of the monorepo reorganization — the npm release automation. **Stacked on #208** (the move); this PR's diff is only the release-please machinery. Retarget its base to `main` once #208 merges. Adds release-please as a single, path-scoped component: it tags `package-vX.Y.Z` — continuing the existing `package-v1.2.0 … package-v3.0.1` series, separate from the gem's `vX.Y.Z` — maintains `javascript/CHANGELOG.md`, and publishes to npm via OIDC trusted publishing (no stored token). The manifest is seeded at the last published version `3.0.1`, and a per-package `release-as: "4.0.0"` makes release-please's first release publish `4.0.0` (which is not on npm yet). The override is necessary because the breaking `chore(npm)!` commit predates the `javascript/` move, so release-please's path-based commit analysis wouldn't attribute it to the package and compute `4.0.0` on its own. ## Around merge - [x] npm trusted publisher registered on npmjs (repo + `release-please.yml`). - [x] Enable Settings → Actions → General → "Allow GitHub Actions to create and approve pull requests" (else release-please can't open its release PR). - [ ] After merge, confirm release-please opens a `4.0.0` release PR; merging it tags `package-v4.0.0` and publishes `4.0.0`. - [ ] Remove `release-as` from `release-please-config.json` after that PR merges — it does not self-clear, or it will keep forcing `4.0.0`. - [ ] Update branch-protection required checks to the new job names (`RSpec`, `Standard`, `Build`, `Vitest`, `Prettier`).
tvdeyen
added a commit
that referenced
this pull request
Sep 2, 2026
🤖 I have created a release *beep* *boop* --- ## [4.0.0](package-v3.0.1...package-v4.0.0) (2026-09-01) ### ⚠ BREAKING CHANGES * `deserializePage`/`deserializePages` no longer filter deprecated content; they are now deprecated aliases for `deserialize` ([#201](#201)) * an `exports` map restricts imports to the package root and `./deserialize` ([#202](#202)) ### Bug Fixes * **deserialize:** break reference cycles to prevent stack overflow ([#200](#200)) ([f7147ae](f7147ae)) ### Code Refactoring * **ts:** migrate deserializer to TypeScript with typed distribution ([#202](#202)) ([3b93397](3b93397)) * stop filtering deprecated content in the deserializer ([#201](#201)) ([40b9145](40b9145)) * move npm package into javascript/ ([#208](#208)) ([44fd9a6](44fd9a6)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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
1 participant
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.
Stage 1 of a two-stage monorepo reorganization — the move. Stage 2 (release-please automation) is stacked on top as a separate PR so this mechanical change can be reviewed and merged on its own.
The repository ships two independently-consumed packages — the
alchemy-json_apiRuby gem and the@alchemy_cms/json_apinpm package — with conflated layout and CI. This stage relocates the npm package intojavascript/(puregit mv— no content changes,dist/byte-identical), splits the sharedREADME/CHANGELOGso each package documents itself, and splits CI into language-scoped, path-filtered workflows so a JS-only change no longer runs the Ruby matrix and vice versa. The gem stays at the repo root, untouched; there are no versioning or release changes here.Verified locally
javascript/: typecheck, 17 tests, prettier, and build all green; committeddist/matches a fresh build.actionlintclean.Note: the JS CI job names change (
Build,Vitest,Prettiernow under theJavaScriptworkflow;RSpec/Standardunchanged). Branch-protection required checks may need updating, and because the workflows are path-filtered, single-language PRs won't produce the other language's checks — so cross-language checks shouldn't be marked blocking-required.