Skip to content

Conversation

@vineetbansal
Copy link
Collaborator

This seems to be a good solution for explicit and manual release, auto-generation of a CHANGELOG. We just need to make sure that we create a new tag (specifying the version in a proper format) when we do a new release.

Screenshot from 2026-02-05 10-22-11 Screenshot from 2026-02-05 10-22-11

This creates a git tag on the HEAD and runs the steps. This is important because all internal tooling uses the (new) git tag to determine what the version number is.

@rkingsbury rkingsbury merged commit 5dbab8a into KingsburyLab:main Feb 5, 2026
14 checks passed
@codecov
Copy link

codecov bot commented Feb 5, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.43%. Comparing base (d60d247) to head (69e7a90).
⚠️ Report is 16 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #327   +/-   ##
=======================================
  Coverage   86.43%   86.43%           
=======================================
  Files          14       14           
  Lines        1851     1851           
  Branches      320      320           
=======================================
  Hits         1600     1600           
  Misses        207      207           
  Partials       44       44           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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.

2 participants