Releases: ru551n/vsg-rs
Releases · ru551n/vsg-rs
Release list
v0.9.6
v0.9.5
- The GitHub Action resolves its suggestion threads that no longer apply on each run (and
reopens one when the same suggestion applies again), so only open problems stay expanded. - The documentation's workflow examples report without code scanning, which stays optional.
- The alignment of
:in generic, port and parameter lists (entity_017,component_017,
procedure_410) and of=>in maps (instantiation_010) can be disabled, and
group: alignment: disablenow turns it off too.
v0.9.4
Less noise on pull requests.
- SARIF reports combine layout findings on adjacent lines into one
formatresult per block,
naming the VSG rules involved; rule violations stay one result each. - The GitHub Action posts layout changes as suggested changes in one review (
layout: suggestions, the default) instead of code scanning alerts, keeps one summary comment per
pull request up to date (pr-comment), and annotates only the lines a pull request adds or
changes (annotations: changed).
v0.9.3
- SARIF reports describe each rule (name, description and a link to VSG's documentation), so
code scanning alerts and pull request comments show which rule was violated. - The README explains how to use the GitHub Action.
v0.9.2
- A GitHub Action (
uses: ru551n/vsg-rs@v0.9.2): downloads the release binary, runs vsg-rs,
shows findings as annotations and in the job summary, and optionally uploads them to code
scanning. Seedocs/github-action.md. - SARIF reports use paths relative to the working directory with
/separators (as code
scanning expects), andfile://URIs for files outside it.
v0.9.1
- The standalone binary archives on GitHub releases get build provenance attestations too
(0.9.0 attested only the Python packages).
v0.9.0
- VSG local rules (
-lr DIR,local_rules: DIR) are supported: vsg-rs runs them with an
installed VSG (vsg, or the command inVSG_RS_VSG) with the built-in rules disabled, adds
their findings to its report and, with--fix, applies their fixes before its own. - Settings of rules vsg-rs does not know no longer cause warnings when local rules are used.
-ocincludeslocal_rules.- Release artifacts get build provenance attestations now that the repository is public.
v0.8.0
Performance.
- Several files are checked and fixed in parallel worker processes instead of threads. The
parser's global token interner made threads contend on every token: VUnit's 222 files now
take 0.6 s instead of 1.7 s, with 3.7 s of CPU time instead of 30 s. The cross-file
declaration index is built by the workers too. --debugprints how long the declaration index took and how many processes were used.
v0.7.0
Command line and distribution.
file_listin the configuration is supported as in VSG: paths and glob patterns (with
environment variables), each optionally with its ownruleblock, checked together with the
files on the command line.--recursivechecks the VHDL files in directories given as inputs.- macOS wheels (arm64 and x86_64) on PyPI.
- pre-commit hooks
vsg-rsandvsg-rs-fix(.pre-commit-hooks.yaml). - A migration guide from VSG (
docs/migrating-from-vsg.md), with CI and pre-commit setups.
v0.6.0
Formatter options.
number_of_spacesof VSG's 175 spacing rules sets the spaces between the tokens each rule is
about, within its construct;>=Nkeeps wider source spacing. The token pairs are generated
from VSG's rule documentation (scripts/gen_spacing_rules.py).port_007toport_009spaces_before/spaces_afterset the spaces around port modes.action: same_lineingeneric_010,port_014,generic_map_004andport_map_004keeps
the closing parenthesis on the last element's line.align_left: 'yes'withalign_paren: 'no'inconcurrent_003orsequential_004indents
continuation lines one level instead of aligning them.- The randomized fix test and the corpus example (
CONFIG=file) cover these options.