Skip to content

Release workflows for @genclass/nuxt, @genclass/astro and @genclass/sv - #261

Open
MeharPro wants to merge 1 commit into
mainfrom
chore/release-nuxt-astro-sv
Open

MeharPro wants to merge 1 commit into
mainfrom
chore/release-nuxt-astro-sv

Conversation

@MeharPro

Copy link
Copy Markdown
Contributor

@genclass/nuxt, @genclass/astro and @genclass/sv are not on npm, so the drafted directory listings (nuxt.com/modules, astro.build/integrations, the Svelte CLI's sv-add keyword) cannot happen. This adds a release workflow for each, after release-playwright.yml.

What is in it

  • release-nuxt.yml (nuxt-v*), release-astro.yml (astro-v*), release-sv.yml (sv-v*): the tag's version must equal the package's, typecheck, build, tests, pack, the tarball kept as an artifact for the first publish, publish with provenance, then a check of what npm serves. The prefixes collide with no existing tag or trigger (v*, cli-v*, mcp-v*, playwright-v*, runtime-model-v*, situation-v*).
  • Added to the pattern, before anything is published:
    • the runtime this repository builds and the one @genclass/runtime@beta installs must be on npm inside the peer range (Nuxt, Astro) or the range the add-on writes (Svelte);
    • the packed tarball is installed next to that runtime and imported (Nuxt, Astro);
    • the packed add-on is applied to a new SvelteKit app through the Svelte CLI npm serves that day (the e2e applies the sources with the pinned CLI);
    • a CHANGELOG heading still marked "(unreleased)" stops the run, so the three headings are now plain ## 0.1.0.
  • packages/sv/package.json: exports named ./dist/index.d.ts, a file the build never writes. The entry is removed.
  • AGENTS.md rule 9 and the repo map name the workflows (and release-playwright.yml, which rule 9 left out); the three listing drafts name the workflow each one waits for.

Checked

package typecheck build tests
@genclass/nuxt (Node 24.15) clean ok 8 of 8
@genclass/astro (Node 24.15) clean ok 10 of 10
@genclass/sv (Node 22.23) clean ok unit 24 of 24
  • The peer range >=0.3.0-beta.1 and the add-on's ^0.3.0-beta.1 both resolve to 0.3.0-beta.7, npm's beta.
  • Run locally from the workflow files, under bash -eo pipefail: the tag and range step, Pack and the tarball install step, for all three. The refusals fire on a wrong tag, an "(unreleased)" heading, an export naming a file that is not packed, and a range npm's beta is outside.
  • Not run: the Svelte add-on's end-to-end test (pnpm, Chromium; sv-addon.yml runs it here), the publish and registry-verify steps, and the workflows on GitHub.

After the merge (owner)

  1. npm-publish environment: allow the tag rules nuxt-v*, astro-v*, sv-v*.
  2. One tag per package on main: nuxt-v0.1.0, astro-v0.1.0, sv-v0.1.0. Each run uploads its tarball (nuxt-tarball, astro-tarball, sv-tarball) and then fails at "Publish with provenance", which is expected for a first version.
  3. Publish each tarball once from an npm login, then set trusted publishing for the package (organization genclass-dev, repository GenClass, its workflow file, environment npm-publish). Each workflow's header has the steps.

Nothing is submitted to any directory from this repository.

🤖 Generated with Claude Code

…v (nuxt-v*, astro-v*, sv-v* tags)

None of the three is on npm, so the drafted directory listings (nuxt.com/modules, astro.build/integrations, the
Svelte CLI's sv-add keyword) could not happen. Each workflow follows release-playwright.yml: the tag's version must
equal the package's, typecheck, build, tests, pack, the tarball kept as an artifact for the owner's first publish,
then publish with provenance and a check of what npm serves.

Added to the pattern, before anything is published:
- the runtime this repository builds and the one `@genclass/runtime@beta` installs must be on npm inside the
  package's peer range (nuxt, astro) or the range the add-on writes (sv);
- the packed tarball is installed next to that runtime and imported (nuxt, astro); the packed add-on is applied to a
  new SvelteKit app through the Svelte CLI npm serves that day (sv; the e2e applies the sources with the pinned CLI);
- a CHANGELOG heading still marked unreleased stops the run, so the three headings are now plain `## 0.1.0`.

@genclass/sv: `exports` named ./dist/index.d.ts, which the build never writes; the entry is removed.

AGENTS.md rule 9 and the repo map name the workflows (and release-playwright.yml, which rule 9 left out); the listing
drafts name the workflow each one waits for.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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.

1 participant