Repository navigation
chore: bump Request Scan to 0.4.2 - #122
Merged
Merged
Conversation
MantisClone
requested review from
LeoSlrRf,
aimen74,
bassgeta and
rodrigopavezi
October 30, 2026 21:24
[Low impact] This version-only change appears safe to merge. SummaryUpdates Request Scan’s application version from
Reviews (1) · Last reviewed commit: "chore: bump Request Scan to 0.4.2" · Reviewed by Greptile |
rodrigopavezi
approved these changes
Oct 30, 2026
Contributor
Author
Merge activity
|
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.

Problem
Request Scan still displays
0.4.1after the REQ-719 security update.Proposed Solution
Bump the application version to
0.4.2inpackage.jsonand both root version entries inpackage-lock.json.Design Rationale
A patch version identifies the security release in the existing footer.
Considerations
Version consistency, formatting, and diff checks passed. All dependency entries and other package settings are unchanged.
UAT: After the staging deployment, open Request Scan and confirm the footer displays
0.4.2.