release: bump 0.1.1 -> 0.1.2 - #119
Merged
Merged
Conversation
The wasm publish step passed the packed tarball to `npm publish` as a bare relative path (`dist/wickra-backtest-wasm-<version>.tgz`). npm parses an argument of that shape as the `owner/repo` GitHub shorthand rather than as a file, so it ran `git ls-remote ssh://git@github.com/dist/...` and exited with code 128 before reaching the registry. A leading `./` marks it as a path. This is what broke the 0.1.1 release. The step had never run under a tag -- `release.yml` executes only on `v*` -- and the publish jobs are independent of one another, so crates.io, PyPI, npm, NuGet and Maven Central published while `wasm-publish` failed. `github-release` depends on every publish job, so it was skipped, which left 0.1.1 without a GitHub release and without the C ABI archives. r-universe resolves the C ABI from the release matching `DESCRIPTION`, so its R builds have been failing on a 404 since. None of that can be withdrawn, so the changelog says plainly what 0.1.1 is missing and points at 0.1.2. ARCHITECTURE.md now records that the publish jobs are independent, since that is what turns one failing step into a half-published release.
Twenty declarations across six package managers, produced by the bump script: the workspace and its path deps, the Python, Node, Java, C# and R manifests, the six per-platform npm packages, both lockfiles, `CITATION.cff` with its `date-released`, the version references in `SECURITY.md`, and the `Cargo.lock` workspace entries via a `cargo build`. `scripts/check_version_sync.py` reports all twenty in agreement. 0.1.2 exists because 0.1.1 shipped incomplete. Its wasm publish step handed `npm publish` a bare relative path, npm read it as an `owner/repo` shorthand and tried to clone it, and the step died before reaching the registry. The publish jobs do not depend on one another, so crates.io, PyPI, npm, NuGet and Maven Central had already published; `github-release`, which needs all of them, was skipped. 0.1.1 therefore has no GitHub release, no C ABI archives and no `wickra-backtest-wasm` package, and r-universe has been resolving its C ABI into a 404 ever since. None of that can be withdrawn, so the changelog states plainly what 0.1.1 is missing and points at this release. No tag is pushed by this.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Twenty declarations across six package managers, produced by the bump script:
the workspace and its path deps, the Python, Node, Java, C# and R manifests, the
six per-platform npm packages, both lockfiles,
CITATION.cffwith itsdate-released, the version references inSECURITY.md, and theCargo.lockworkspace entries via a
cargo build.scripts/check_version_sync.pyreportsall twenty in agreement.
0.1.2 exists because 0.1.1 shipped incomplete. Its wasm publish step handed
npm publisha bare relative path, npm read it as anowner/reposhorthand andtried to clone it, and the step died before reaching the registry. The publish
jobs do not depend on one another, so crates.io, PyPI, npm, NuGet and Maven
Central had already published;
github-release, which needs all of them, wasskipped. 0.1.1 therefore has no GitHub release, no C ABI archives and no
wickra-backtest-wasmpackage, and r-universe has been resolving its C ABI intoa 404 ever since. None of that can be withdrawn, so the changelog states plainly
what 0.1.1 is missing and points at this release.
No tag is pushed by this.