fix: use target-bounded source validation compiler#4
Merged
Conversation
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
Fixes #3.
Broad source pragmas now keep two separate concepts:
The per-file report now records the original source version spec and resolved source compiler, and human output labels source compilation with the resolved compiler when known.
Validation
uv run --locked ruff check src tests scripts/corpus.py scripts/release_notes.pyuv run --locked pytestscripts/smoke-wheel.shvyperlang/vyperexamples/tokens/ERC20.vyand ranuv run --locked vyupgrade --check /tmp/vyupgrade-ERC20.vy --report-json /tmp/vyupgrade-erc20-report.jsonERC20 result: only
VY001, source compile used0.4.3, target compile passed, ABI/method IDs/storage layout unchanged, and no diagnostics.