feat: publish @next builds to GitHub Packages on develop pushes - #10
Merged
Merged
Conversation
Add a publish-next workflow that snapshot-versions and publishes the package to GitHub Packages under the next dist-tag on every push to develop. Rename the package to @kamsteegsoftware/fetchify since GitHub Packages requires the npm name to be scoped to the org, and update pending changesets/docs accordingly.
joeykamsteeg
added a commit
that referenced
this pull request
Aug 2, 2026
All 11 tasks complete; live-verified the publish-next workflow via the automatic push-to-develop trigger (PR #10) rather than manual dispatch, since GitHub only allows workflow_dispatch for workflows already present on the default branch.
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
.github/workflows/publish-next.yml: on every push todevelop(or manualworkflow_dispatch), builds the package, computes a snapshot pre-release version viachangeset version --snapshot next, and publishes to GitHub Packages under thenextdist-tag.@kamsteegsoftware/fetchify— required for GitHub Packages to accept the publish. UpdatesDOCS.mdimport examples and pending changeset frontmatter accordingly.Full proposal/design/spec/tasks are under
openspec/changes/publish-next-github-packages/.Test plan
bun run build,bun test(39 pass),bun run lintall pass after the renamechangeset version --snapshot next --snapshot-prerelease-template "{tag}-{commit}"succeeds and produces e.g.0.0.0-next-<commit-sha>once the pending changesets' package key was updatedPublish nextworkflow run succeeds ondevelopand the package appears in GitHub Packages under thenexttagdevelop'spackage.jsonversion is unchanged post-run (snapshot bump isn't committed)🤖 Generated with Claude Code