Security/640 resolve vulnerability with pip#641
Merged
Conversation
ArBridgeman
temporarily deployed
to
manual-approval
GitHub Actions
Inactive
ArBridgeman
commented
Oct 30, 2025
| def pre_integration_tests_hook(self, session, config, context): | ||
| port = context.get("port", 8563) | ||
| db_version = context.get("db_version", "7.1.17") | ||
| db_version = context.get("db_version", "2025.1.0") |
Collaborator
Author
There was a problem hiding this comment.
As the tests currently succeed with 2025.1.0, we update to this latest version for the default database version when executing the integration tests.
In the future, we can hopefully get this from the PROJECT_CONFIG via the inherited BaseConfig.
ArBridgeman
temporarily deployed
to
manual-approval
GitHub Actions
Inactive
ArBridgeman
force-pushed
the
security/640_resolve_vulnerability_with_pip
branch
from
b94dde1 to
e13ecb9
Compare
ArBridgeman
temporarily deployed
to
manual-approval
GitHub Actions
Inactive
- This is a dev dependency, and we did not update the pyproject.toml. We will see if sqlalchemy 2.x migration resolves the issue. If not, then an issue can be created to look into this.
ArBridgeman
force-pushed
the
security/640_resolve_vulnerability_with_pip
branch
from
e13ecb9 to
33993b5
Compare
ArBridgeman
temporarily deployed
to
manual-approval
GitHub Actions
Inactive
ArBridgeman
commented
Oct 30, 2025
| steps: | ||
| - name: SCM Checkout | ||
| uses: actions/checkout@v4 | ||
| uses: actions/checkout@v5 |
Collaborator
Author
There was a problem hiding this comment.
workflow updates are triggered by poetry run -- tbx workflow update and are hand-checked that custom functionality was not lost
|
pj-spoelders
approved these changes
Oct 30, 2025
This was referenced Oct 30, 2025
Closed
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
2 participants
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.
closes #640
Checklist
Note: If any of the items in the checklist are not relevant to your PR, leave the box unchecked.
For any Pull Request
Is the following correct:
When Changes Were Made
Did you:
When Preparing a Release
Have you: