Skip to content

Release v0.3.0: fail release on upload errors, correct action pin comments - #3

Merged
sionsmith merged 1 commit into
mainfrom
release/v0.3.0
Oct 12, 2026
Merged

sionsmith merged 1 commit into
mainfrom
release/v0.3.0

Conversation

@sionsmith

Copy link
Copy Markdown
Contributor

Summary

Prepares the v0.3.0 release from current main and closes out the CI/release workflow follow-ups from the SHA pinning.

  • Version bump to 0.3.0 (workspace Cargo.toml, Cargo.lock, README). The v0.2.x tags were cut while the workspace still said 0.1.0, so wpx --version reported 0.1.0. main now has custom post type routing (--type blog), content files, media upload and wpx api, so this is a minor bump.

  • release.yml: a failed asset upload now fails the job. Removed || true from gh release upload.

  • release.yml: build now needs: create-release. The two jobs ran in parallel and || true hid the race. Without it, an upload that beat the release creation would fail the job.

  • Pin comments corrected, SHAs unchanged. I checked each pinned uses: against upstream:

    Action SHA Was commented Actually is
    actions/checkout 34e11487… v4 tag v4.3.1 (the v4 tag has since moved to v4.4.0)
    dtolnay/rust-toolchain 3c5f7ea2… stable a master commit (27 Mar 2026), not the stable branch, so it has no default toolchain input
    Swatinem/rust-cache e18b4977… v2 v2.9.1 plus one CHANGELOG-only commit on master

The two failed CI runs

  • 23976944321 (push to main, 4 Apr, "fix: pin GitHub Actions to immutable commit SHAs"). All four jobs failed within seconds at the dtolnay/rust-toolchain step. The logs have expired (HTTP 410), but the annotations point to the toolchain-parse line. The same cause is visible in the next run.
  • 37776243559 (PR Custom post type routing, content files, media upload, raw api command, env credentials #1, 8 Oct). The log shows 'toolchain' is a required input: the pinned SHA is a master commit, which has no default toolchain.
  • Both were fixed in 4861c1b (9 Oct), which passes toolchain: stable explicitly in ci.yml and release.yml, and the 9 Oct runs on main are green. The comment fix here stops anyone removing that input later because they think it is redundant.

Local checks

cargo check, cargo test --workspace (all pass), cargo clippy --workspace -- -D warnings, cargo fmt --all -- --check, wpx man --dir and actionlint are all clean.

🤖 Generated with Claude Code

…n comments

- Bump the workspace version from 0.1.0 to 0.3.0 (Cargo.toml, Cargo.lock,
  README). v0.2.x binaries still reported 0.1.0; main now carries custom post
  type routing, content files, media upload and `wpx api`.
- release.yml: drop `|| true` from `gh release upload` so a failed upload
  fails the build job instead of silently shipping a release without assets.
- release.yml: build now `needs: create-release`. The two jobs ran in
  parallel and `|| true` hid the race; without it an upload that beat the
  release creation would fail.
- ci.yml / release.yml: the version comments on the pinned SHAs did not
  match what the SHAs are. Verified each against upstream:
  - actions/checkout 34e11487 is tag v4.3.1 (the v4 tag has since moved).
  - dtolnay/rust-toolchain 3c5f7ea2 is a master commit (27 Mar 2026), not
    the `stable` branch, which is why it has no default `toolchain` input
    and why CI failed until `toolchain: stable` was added.
  - Swatinem/rust-cache e18b4977 is v2.9.1 plus one CHANGELOG-only commit
    on master.
  SHAs are unchanged; only the comments are corrected.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sionsmith
sionsmith merged commit 1f99dc1 into main Oct 12, 2026
4 checks passed
@sionsmith
sionsmith deleted the release/v0.3.0 branch October 12, 2026 11:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant