Skip to content

release: v0.3.1 — first stable v0.3.x on @latest#759

Merged
kokevidaurre merged 3 commits intomainfrom
release/v0.3.1
Apr 24, 2026
Merged

release: v0.3.1 — first stable v0.3.x on @latest#759
kokevidaurre merged 3 commits intomainfrom
release/v0.3.1

Conversation

@kokevidaurre
Copy link
Copy Markdown
Contributor

Summary

Bumps to 0.3.1. Skipping 0.3.0 because that slot is reserved by a deprecated historical pre-release (Jan 2026 cleanup). npm enforces version immutability, so we cannot republish 0.3.0.

0.3.1 is the smallest available version after 0.3.0-rc.1 in the v0.3.x line.

Why this works

  • Tag v0.3.1 is clean semver (no - suffix) → release.yml publishes to @latest via OIDC
  • Content is identical to 0.3.0-rc.1 (already burned in on @next)
  • Existing @next users on 0.3.0-rc.1 continue to work; they can move to @latest with npm i -g squads-cli@latest

Post-merge steps

git checkout main && git pull
git tag v0.3.1
git push origin v0.3.1   # release.yml publishes 0.3.1 to @latest

Test plan

  • CI green
  • After tag push: npm view squads-cli dist-tags shows latest: 0.3.1
  • npm i -g squads-cli (no tag) installs 0.3.1
  • squads --version outputs 0.3.1

Skipping 0.3.0 because that version slot was claimed by a deprecated
historical pre-release (Jan 2026, deprecated as part of the
"deprecate all pre-release versions 0.3.0-0.6.2" cleanup). npm
enforces version immutability — we cannot republish 0.3.0.

0.3.1 is the smallest available version after rc.1 in the 0.3.x line.
After merge, tag v0.3.1 → release.yml publishes to @latest via OIDC.

Same content as the rc.1 burn-in candidate (0.3.0-rc.1 on @next).

Co-Authored-By: Claude <noreply@anthropic.com>
@codecov-commenter
Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Hand-curated changelog covering 0.2.1 → 0.3.1. Notes the deprecated
historical pre-releases (0.3.0, 0.4.x, 0.5.x, 0.6.x, 0.7.0) so users
don't accidentally install them.

GitHub Releases remain the canonical record (auto-generated by
release.yml on tag push); this file is the human-readable summary
and lives in the package itself (npm view shows it).

Co-Authored-By: Claude <noreply@anthropic.com>
@github-actions github-actions Bot added the docs label Apr 24, 2026
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the version of the squads-cli package from 0.3.0 to 0.3.1 in both package.json and package-lock.json. A critical security concern was raised regarding the presence of several dependency versions (such as @anthropic-ai/sdk ^0.71.2 and vitest ^4.0.16) that do not exist on the public npm registry, which may indicate a dependency confusion or supply chain attack.

Comment thread package.json
{
"name": "squads-cli",
"version": "0.3.0",
"version": "0.3.1",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

security-critical critical

The version bump is consistent, but the project's dependencies and lockfile contain several version numbers that do not exist on the public npm registry (e.g., @anthropic-ai/sdk ^0.71.2, vitest ^4.0.16, eslint ^9.39.2, and typescript resolved to 5.9.3 in package-lock.json). This is a critical security indicator of a potential dependency confusion attack or a compromised supply chain. Please verify the legitimacy of these versions and ensure they are sourced from a trusted registry before proceeding with this release.

Surfaces the canonical changelog, releases, and issues URLs at the
bottom of \`squads --help\` so users discover them without hunting.

Co-Authored-By: Claude <noreply@anthropic.com>
@github-actions github-actions Bot added the core label Apr 24, 2026
@kokevidaurre kokevidaurre merged commit d79b06c into main Apr 24, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants