Repository navigation
Conversation
…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
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.
@genclass/nuxt,@genclass/astroand@genclass/svare not on npm, so the drafted directory listings (nuxt.com/modules, astro.build/integrations, the Svelte CLI'ssv-addkeyword) cannot happen. This adds a release workflow for each, afterrelease-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*).@genclass/runtime@betainstalls must be on npm inside the peer range (Nuxt, Astro) or the range the add-on writes (Svelte);## 0.1.0.packages/sv/package.json:exportsnamed./dist/index.d.ts, a file the build never writes. The entry is removed.release-playwright.yml, which rule 9 left out); the three listing drafts name the workflow each one waits for.Checked
@genclass/nuxt(Node 24.15)@genclass/astro(Node 24.15)@genclass/sv(Node 22.23)>=0.3.0-beta.1and the add-on's^0.3.0-beta.1both resolve to0.3.0-beta.7, npm'sbeta.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'sbetais outside.sv-addon.ymlruns it here), the publish and registry-verify steps, and the workflows on GitHub.After the merge (owner)
npm-publishenvironment: allow the tag rulesnuxt-v*,astro-v*,sv-v*.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.npm-publish). Each workflow's header has the steps.Nothing is submitted to any directory from this repository.
🤖 Generated with Claude Code