Skip to content

Bump version v2.5.0 -> v3.0.0a0#741

Merged
danielhollas merged 1 commit into
masterfrom
release/3.0.0a0
Apr 10, 2026
Merged

Bump version v2.5.0 -> v3.0.0a0#741
danielhollas merged 1 commit into
masterfrom
release/3.0.0a0

Conversation

@danielhollas

@danielhollas danielhollas commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

Let's release a 3 alpha version for an easier testing with the nbclassic image

(needs to be merged with a merged commit!)

@codecov

codecov Bot commented Apr 9, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.77%. Comparing base (68d9e6e) to head (da54f24).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #741   +/-   ##
=======================================
  Coverage   84.77%   84.77%           
=======================================
  Files          18       18           
  Lines        3336     3336           
=======================================
  Hits         2828     2828           
  Misses        508      508           
Flag Coverage Δ
python-3.11 84.74% <100.00%> (ø)
python-3.12 84.74% <100.00%> (ø)
python-3.9 84.75% <100.00%> (+0.36%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

@edan-bainglass edan-bainglass left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

👍 but why merge commit?

@danielhollas

Copy link
Copy Markdown
Contributor Author

@edan-bainglass good question, tl;dr is that the commit in this PR is already tagged, so squashing or rebasing would create a new commit and we would lose the tag (or rather the tag would stay on github but would point to a commit that's not on a main branch)

I ran bumpver as

bumpver update  --major --tag alpha

The current release process is described on the wiki: https://github.com/aiidalab/aiidalab/wiki/Development-guide#releasing-a-new-version

We should make it less complicated, happy to discuss at some point when you have time.

@danielhollas danielhollas merged commit 2d12ff0 into master Apr 10, 2026
15 checks passed
@danielhollas danielhollas deleted the release/3.0.0a0 branch April 10, 2026 05:24
@danielhollas

Copy link
Copy Markdown
Contributor Author

New release is now available 🚀

https://github.com/aiidalab/aiidalab-widgets-base/releases/tag/v3.0.0a0

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