Skip to content

chore: Update @casl/ability from 6.7.3 to 6.8.0#2259

Merged
caneppelevitor merged 1 commit intostagefrom
chore/casl-ability-update
Feb 25, 2026
Merged

chore: Update @casl/ability from 6.7.3 to 6.8.0#2259
caneppelevitor merged 1 commit intostagefrom
chore/casl-ability-update

Conversation

@lucaslobatob
Copy link
Collaborator

Description

This PR updates the @casl/ability dependency from version 6.7.3 to 6.8.0, incorporating internal improvements, bug fixes, and minor typing and stability enhancements introduced in the new release. The update does not alter the existing authorization logic or impact the rules defined in the project, maintaining the current behavior and ensuring greater alignment with the latest versions of the ecosystem.

Related Ticket #2258

Type of change

  • Bug fix (non-breaking change which fixes an issue)

Testing

Provide relevant testing instructions. What scenarios are impacted? What build may be necessary to test this change?

Developer Checklist

General

  • No console.log or related logging is added.
  • No code is repeated/duplicated in violation of DRY. The exception to this is for new (MVP/Prototype) functionality where the abstraction layer may not be clear (comments should be added to explain the violation of DRY in these scenarios).

Tests

  • All existing unit and end to end tests pass across all services
  • Unit and end to end tests have been added to ensure backend APIs behave as expected

Test IDs

  • Include the test ID when adding new tasks or components.
  • Check that test IDs are present in the modified components.

Merge Request Review Checklist

  • An issue is linked to this PR and these changes meet the requirements outlined in the linked issue(s)
  • High risk and core workflows have been tested and verified in a local environment.
  • Enhancements or opportunities to improve performance, stability, security or code readability have been noted and documented in Project do Github issues if not being addressed.
  • Any dependent changes have been merged and published in downstream modules
  • Changes to multiple services can be deployed in parallel and independently. If not, changes should be broken out into separate merge requests and deployed in order.

@caneppelevitor caneppelevitor merged commit a1042f2 into stage Feb 25, 2026
7 of 9 checks passed
@LuizFNJ LuizFNJ mentioned this pull request Feb 25, 2026
46 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: QA

Development

Successfully merging this pull request may close these issues.

2 participants