ci: add auto-publish workflow on merge to main#41
Merged
Conversation
- Trigger on push to main when package.json changes (instead of release creation) - Use Bun for dependency installation - Run type check, lint, and build before publishing - Enable npm provenance via OIDC (id-token: write) - Use NPM_TOKEN secret for authentication
vorflux
Bot
changed the title
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.
Summary
Replaces the existing bare-bones
npm-publish.yml(which triggered on release creation and usednpm ci) with a proper auto-publish workflow (publish.yml) that:mainwhenpackage.jsonchanges (version bump = auto-publish)id-token: write)NPM_TOKENsecret for authenticationNote: The
build:libstep is intentionally omitted becauselib/validate.tsis gitignored (lib/*.tsin.gitignore) and the compiledlib/validate.jsis committed directly to the repo.Testing
This is a workflow file change -- validated YAML syntax and confirmed it follows the same pattern used across other supermemoryai repos (
supermemory/publish-ai-sdk.yml).Session Details
(aside)to your comment to have me ignore it.