fix: pass built version to dev verification - #422
Merged
Paulo Lacerda (placerda) merged 1 commit intoAug 14, 2026
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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
1 participant
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.
Summary
publish-devverify-devinstead of recomputing it with setuptools-scmRoot cause
When
developpoints exactly at a release tag, build isolation can produce the tagged release version while a fresh setuptools-scm invocation predicts the next development version. The two jobs therefore disagreed about which TestPyPI package to verify.Validation
python -m pytest tests\unit\test_ci_workflow.py -q(2 passed)python -m pytest tests\ -x -q(1319 passed, 1 skipped)python -m ruff check src\ tests\python -m mypy src\agentops\ --ignore-missing-importspython scripts\check_changelog.py check-pr --base origin/develop