Skip to content

feat(forgejo): add the Forgejo SDK on alchemy-pointer - #559

Closed
wyattjoh wants to merge 1 commit into
alchemy-run:alchemy-pointerfrom
wyattjoh:wyattjoh/forgejo-on-alchemy-pin
Closed

feat(forgejo): add the Forgejo SDK on alchemy-pointer#559
wyattjoh wants to merge 1 commit into
alchemy-run:alchemy-pointerfrom
wyattjoh:wyattjoh/forgejo-on-alchemy-pin

Conversation

@wyattjoh

@wyattjoh wyattjoh commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Cherry-picks #550 onto alchemy-pointer. The packages/forgejo tree is identical to main's — only the branch it sits on differs.

alchemy-pointer is what alchemy's submodules/distilled gitlink tracks, and it's 60 commits behind main. Repinning alchemy at main to pick up Forgejo would drag in every other SDK's regeneration and drop 894211f (fix(railway): drop admin-only platformFeatureFlags), which alchemy-run/alchemy#1479 landed for.

Three adaptations for this branch:

  • stacks/distilled-submodules/spec-repos/forgejo is omitted — the spec-mirror stack doesn't exist here
  • .gitmodules and the root tsconfig.json take only the Forgejo entries
  • the packages/forgejo lockfile importer takes this branch's resolved catalog:tooling versions (@types/bun@1.4.0, @types/node@26.4.0), matching every sibling package — main had since floated those latest specifiers to 1.4.1 / 26.4.1

Needed by alchemy-run/alchemy#1425.

Cherry-picks alchemy-run#550. The packages/forgejo tree is identical to main's; the
spec-mirror stack entry is dropped, and .gitmodules, tsconfig.json, and
the pnpm-lock importer take this branch's layout and its resolved
catalog versions.
@wyattjoh wyattjoh closed this Sep 7, 2026
@wyattjoh
wyattjoh force-pushed the wyattjoh/forgejo-on-alchemy-pin branch from f34e991 to 3b6f324 Compare September 7, 2026 23:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants