Skip to content
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

Slax - Maintenance - July 2024 #433

Closed
3 of 5 tasks
bford002 opened this issue Jul 1, 2024 · 0 comments
Closed
3 of 5 tasks

Slax - Maintenance - July 2024 #433

bford002 opened this issue Jul 1, 2024 · 0 comments
Labels
dependencies Pull requests that update a dependency file maintenance

Comments

@bford002
Copy link
Contributor

bford002 commented Jul 1, 2024

requires Slax dependabot alerts

Background

Slax currently has 0 new security vulnerabilities (0 critical, 0 high, 0 moderate, and 0 low). The purpose of this ticket is to address Slax's security vulnerabilities.

Closed last month: 0
Critical: 0
High: 0
Moderate: 0
Low: 0

Open Dependabot pull requests:
Bump oban from 2.15.4 to 2.17.11
Bump ecto_sql from 3.11.1 to 3.11.3
Bump ex_doc from 0.32.0 to 0.34.1
Bump plug from 1.15.3 to 1.16.1
Bump phoenix from 1.6.16 to 1.7.14
Bump stream_data from 0.6.0 to 1.1.1
Bump phoenix_ecto from 4.4.0 to 4.6.1
Bump castore from 1.0.6 to 1.0.7
Bump plug_cowboy from 2.5.2 to 2.7.1
Bump quantum from 3.4.0 to 3.5.3

Scenario: Update security vulnerabilities

Given I am an Engineer

  • When I manually address dependency conflicts listed here
  • Then I test by running locally
  • And I merge to master and test in production

QA / UAT Note

Remember to add a comment when passing this forward with links to:

  • the review app
  • the pull request itself
@bford002 bford002 added dependencies Pull requests that update a dependency file maintenance labels Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file maintenance
Projects
None yet
Development

No branches or pull requests

3 participants