-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ 4º ] - Hotfix/v2.1.1: Solved vulnerabilities and frontend bugs #212
Merged
Conversation
This file contains 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
Me, @dsrparracho and @saudkhan116 tested this version and everything is ok! |
matbmoser
force-pushed
the
hotfix/v2.1.1
branch
2 times, most recently
from
February 5, 2024 17:48
ce35bc9
to
09bff54
Compare
matbmoser
force-pushed
the
hotfix/v2.1.1
branch
from
February 5, 2024 17:55
09bff54
to
1569e10
Compare
Ok done with the testing everything is fine! |
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.
Why we create this PR?
There is one vulnerability in the application related to the axios library. There several bugs found in the E2E tests in the frontend component, related with the translations.
What we want to achieve with this PR?
Resolve the bugs with the frotend and prepare the release v2.1.1 with all the requirements for the TRGs
What is new?
Added
Updated
v1.6.0
tov1.6.7
to fix vulnerabilityIssues Fixed
Closes #180