Release v1.1.0rc3 - #290
Merged
Merged
Conversation
|
wkirui
approved these changes
Sep 21, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Pull Request Summary 🚀
What does this PR do? 📝
Bumps the version from
1.1.0rc2to1.1.0rc3, now that both #288(rc2 changelog/version bump) and #289 (project configuration
export/import + redesigned project picker) are merged to
main.Why is this change needed? 🤔
1.1.0rc2was tagged before #289 merged, so the new projectconfiguration export/import feature and the redesigned project picker
weren't part of any published pre-release yet. This rc build makes them
available on Test PyPI for the team to try out.
How was this implemented? 🛠️
origin/maindirectly (after confirming both Release v1.1.0rc2 #288 andfeat: export/import project configuration + redesigned project picker #289 were merged, and that the changelog merge conflict between them
had already been resolved on
main)just bump-and-tag rc(uv version --bump rcunder the hood) tobump
pyproject.tomlfrom1.1.0rc2to1.1.0rc3, re-synceduv.lock, and created thev1.1.0rc3tag (already pushed, triggeringthe Release workflow / Test PyPI publish)
How to test or reproduce ? 🧪
This PR (version bump only, no source changes):
just lint-py— passesjust test— full suite greenjust check-changelog rc—[Unreleased]gate passesjust version— confirms1.1.0rc3The published
1.1.0rc3pre-release itself — once the Releaseworkflow finishes (check Test PyPI: DataSure history):
uv tool install "datasure==1.1.0rc3" --index-strategy unsafe-best-match \ --index https://test.pypi.org/simple/ \ --index https://pypi.org/simple/ datasure --version datasureParticularly worth checking against #289: the redesigned Start page
project picker (search/sort, per-project rows, "More" menu) and the
"New Project" → "From a configuration file" flow end-to-end.
Screenshots (if applicable) 📷
N/A — version-metadata change only, no source change in this PR.
Checklist ✅
🤖 Generated with Claude Code