Skip to content

Slax - Maintenance - May 2026 #587

Description

@quinnmccourt

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 credo from 1.7.15 to 1.7.18
Bump oban from 2.20.2 to 2.21.1
Bump castore from 1.0.17 to 1.0.18
Bump stream_data from 1.2.0 to 1.3.0
Bump phoenix from 1.8.3 to 1.8.5
Bump ecto_sql from 3.13.4 to 3.13.5
Bump plug_cowboy from 2.7.5 to 2.8.0
Bump ex_doc from 0.39.3 to 0.40.1
Bump postgrex from 0.21.1 to 0.22.0

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

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