Repository navigation
chore(release): v0.8.0 (core 0.6.0), and make npm publishing opt-in - #145
Merged
Merged
Conversation
Bumps @ripple-ui/svelte to 0.8.0 and @ripple-ui/core to 0.6.0 for the release that carries the slim headless runtime, the slim manifest and the loop-variable fix for headless handlers (#142, #143). The release workflow used to try npm on every v* tag. Every such run failed without an NPM_TOKEN, and with a token set anywhere a tag would publish whether or not that was intended. npm publishing now runs only on a manual dispatch with publish_npm: true. A tag creates the GitHub release alone. That release now carries a packed tarball of each package next to the manifest bundle, with svelte's core dependency rewritten to ^<core version> as the npm step does, so it can be installed without npm. Simulated on a copy of both packages: ripple-ui-core-0.6.0.tgz and ripple-ui-svelte-0.8.0.tgz, the latter depending on @ripple-ui/core ^0.6.0. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Version bump for the v0.8.0 release, and a change to how releases publish.
Versions:
@ripple-ui/svelte0.7.0 → 0.8.0,@ripple-ui/core0.5.0 → 0.6.0.version.tsis updated with it, andversion.test.tspasses. This release carries:eachget their loop variables in the headless runtime.@ripple-ui/core/headless/slim) and the slim manifest (@ripple-ui/core/manifest,buildSlimManifest).Consumers that install from a checkout (
file:paths) are unaffected by the bump.Release workflow
publish_npm: true. Until now everyv*tag tried npm. Each of those runs failed without anNPM_TOKEN, and once a token is set anywhere (repo or org), a tag would publish whether or not that was meant. This release is GitHub only.ripple-ui-core-<v>.tgzandripple-ui-svelte-<v>.tgz, next to the manifest bundle. Svelte's core dependency is rewritten to^<core version>in the runner, as the npm step already does, so the release can be installed without npm. I simulated the pack step on a copy of both packages: the file names match the release globs, and the svelte tarball depends on@ripple-ui/core ^0.6.0.After this merges I'll push the
v0.8.0tag, which builds and publishes the GitHub release.🤖 Generated with Claude Code