Skip to content

chore: Use the new release of the shared workflows and revert storage limit changes#985

Open
saltiyazan wants to merge 3 commits into
mainfrom
TLSENG-1098
Open

chore: Use the new release of the shared workflows and revert storage limit changes#985
saltiyazan wants to merge 3 commits into
mainfrom
TLSENG-1098

Conversation

@saltiyazan
Copy link
Copy Markdown
Contributor

Description

Please include a summary of the change. Please also include relevant motivation and context. List any dependencies that are required for this change.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • I have added tests that validate the behaviour of the software
  • I validated that new and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have bumped the version of any required library.

@saltiyazan saltiyazan changed the title Use the new release of the shared workflows chore: Use the new release of the shared workflows May 28, 2026
@saltiyazan saltiyazan force-pushed the TLSENG-1098 branch 6 times, most recently from 30780a6 to 65d9ccf Compare May 29, 2026 09:43
@saltiyazan saltiyazan marked this pull request as ready for review May 29, 2026 09:55
@saltiyazan saltiyazan requested a review from a team as a code owner May 29, 2026 09:55
Copy link
Copy Markdown
Contributor

@VercinGor VercinGor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

replacement looks in order

@saltiyazan saltiyazan changed the title chore: Use the new release of the shared workflows chore: Use the new release of the shared workflows and revert storage limit changes May 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants