Skip to content

Slax - Maintenance - January 2025 #479

Closed
@nschello

Description

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

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions