Skip to content

chore(main): release 2.0.0 - #71

Closed
ruby-automation wants to merge 1 commit into
mainfrom
release-please--branches--main
Closed

chore(main): release 2.0.0#71
ruby-automation wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@ruby-automation

@ruby-automation ruby-automation commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

2.0.0 (2026-08-11)

⚠ BREAKING CHANGES

  • graduate to 1.0.0 - disable pre-major version bumping (#70)
  • cd: parallelize Burrito target builds and fix Trivy/Podman image scanning (#68)
  • ci: rename release.yaml to main.yaml, workflow name to "main" (#38)
  • add Readme/LICENSE, feat: wire up the issue list --project picker (#12)

Features

  • add mix githooks.install to activate the repo's git hooks (#51) (9b35472)
  • api: add LinearCli.Api GraphQL client (Phase 1) (723f3f6)
  • ci: add a full SBOM - app deps, OTP/Elixir runtime, container OS packages (#54) (e296fdd)
  • cli: add favorite teams/projects, filtering list views by them (#61) (6c858d9)
  • cli: add issue create/develop/pr/take/update write commands (Phase 6) (1649618)
  • cli: add profiles - default team/project stored in local SQLite (#57) (554e336)
  • cli: add project update - post a status update to a project (#43) (30dc6dc)
  • cli: make version respect --output json (#33) (b160aad)
  • cli: resolve bare issue numbers via active profile, favorited teams, or a team prompt (#65) (8b183da)
  • cli: support Ruby's short subcommand aliases (#15) (9fca6b5)
  • initial commit with ash submodule (c2ceafb)
  • linear: add Ash domain resources for Issue/Project/Team/User/Label/WorkflowState/Comment (Phase 2) (e2a27f3)
  • oban: add scheduled monthly project rollover (Phase 7) (11afb43)
  • phase 4 from initial plan -> complete (012866e)
  • phase 8 - packaging, releasing, and CI (#1) (905c238)
  • scaffold Elixir port and enforce conventional commits (a4d03a0)

Bug Fixes

  • ci: consolidate the release pipeline into one workflow/DAG (ba821bb)
  • ci: create releases as drafts so assets survive Immutable Releases (#19) (8572623)
  • ci: package release binaries with the wrapper scripts (#24) (5fb24a4)
  • ci: rebuild the release pipeline to stop the version-bump runaway loop (#30) (c311fd4)
  • ci: relabel the release PR as tagged after we tag it ourselves (ab1408e)
  • ci: skip commit-subject validation in the post-merge pipeline (#41) (3d00a85)
  • cli: reject unrecognized flags instead of treating them as issue ids (#2) (#4) (e697ff6)
  • deps: update ash to a non-vulnerable version (#63) (b838e2a)

Performance Improvements

  • linear: fan out find-by-ids and per-team project fetches (Phase 5) (fb00153)

Documentation

  • add Readme/LICENSE, feat: wire up the issue list --project picker (#12) (eb42c69)

Miscellaneous Chores

  • ci: rename release.yaml to main.yaml, workflow name to "main" (#38) (2581a40)
  • graduate to 1.0.0 - disable pre-major version bumping (#70) (87a65ae)

Continuous Integration

  • cd: parallelize Burrito target builds and fix Trivy/Podman image scanning (#68) (5cc829a)

This PR was generated with Release Please. See documentation.

@bougyman

bougyman commented Aug 11, 2026

Copy link
Copy Markdown
Member

Closing - this 2.0.0 proposal is a side-effect of manually bumping the manifest to 1.0.0 in the same commit that also carried a ! breaking marker. Pinning the next release to 1.0.0 via release-as instead of letting bump math compound on top of the manual bump.

@bougyman bougyman closed this Aug 11, 2026
@bougyman bougyman mentioned this pull request Aug 11, 2026
Merged
3 tasks
bougyman added a commit that referenced this pull request Aug 11, 2026
@bougyman
chore: pin the next release to 1.0.0 via release-as (#72)
fd56b14 
## Summary
- #70's graduation commit manually set the manifest to `1.0.0` in the
same commit that also carried a `!` breaking-change marker.
Release-please treated that marker as new unreleased work on top of the
manifest we'd already bumped, computing `1.0.0 + major = 2.0.0` (opened
as #71, closed unmerged - never tagged or released, confirmed via `gh
release list`/`git ls-remote --tags`).
- Adds `"release-as": "1.0.0"` to `.release-please-config.json` so
release-please targets exactly `1.0.0` for its next PR instead of
computing a bump on top of the current manifest value.

## Follow-up
Per release-please's own docs, `release-as` should be removed (or
bumped) once the resulting `chore(main): release 1.0.0` PR merges -
otherwise future runs keep reusing this pin instead of computing normal
semver bumps. Tracking this so it doesn't get forgotten.

## Test plan
- [x] JSON validated
- [x] `actionlint` re-run on `.github/workflows/main.yaml` - unaffected,
still clean
- [x] Confirmed no `v2.0.0` tag/release exists anywhere (`gh release
list`, `git ls-remote --tags origin`)

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

autorelease: pending

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ruby-automation @bougyman