Update Dockerfile and configs to latest dependencies and fix deprecated Capybara field #616
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
vanessuniq
changed the title
Dockerfile Signed-off-by: Vanessa Fotso <vfotso@mitre.org>
Signed-off-by: Vanessa Fotso <vfotso@mitre.org>
Signed-off-by: Vanessa Fotso <vfotso@mitre.org>
vanessuniq
force-pushed
the
docker-bundler-update-version
branch
from
c89a5ae
to
509f0fb
Compare
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.
This PR implements several updates and fixes across our configuration files:
Dockerfile Update: The bundled application version has been updated to
2.3.10to ensure compatibility with the latest libraries and security patches.Capybara Field Deprecation: The deprecated
[:capabilities]field in our Capybara setup has been replaced with:optionsto align with the latest syntax and avoid future deprecation issues.Node and Yarn Version Specification: The
package.jsonhas been updated to specify the versions of Node and Yarn we are using. This is to lock the project to stable versions and prevent inconsistencies across development environments.These changes aim to improve our CI/CD pipeline efficiency and ensure a stable development environment for new features.