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 - January 2025 #479

Open
5 tasks
nschello opened this issue Jan 1, 2025 · 0 comments
Open
5 tasks

Slax - Maintenance - January 2025 #479

nschello opened this issue Jan 1, 2025 · 0 comments
Labels
dependencies Pull requests that update a dependency file maintenance

Comments

@nschello
Copy link

nschello commented Jan 1, 2025

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 castore from 1.0.9 to 1.0.11
Bump credo from 1.7.10 to 1.7.11
Bump ex_doc from 0.34.2 to 0.36.1
Bump phoenix from 1.7.14 to 1.7.18
Bump oban from 2.17.12 to 2.18.3
Bump postgrex from 0.19.1 to 0.19.3
Bump stream_data from 1.1.1 to 1.1.2

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
@nschello nschello added dependencies Pull requests that update a dependency file maintenance labels Jan 1, 2025
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

1 participant