fix: actions trigger - #3719
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
portuu3
approved these changes
Dec 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue tracking
N/A/
Context behind the change
In #3685
tag-ignorefilter was introduced and after it all related actions stopped to trigger. GitHub doc saysSo in case when you have just
tags/tags-ignoreit means that GA will consider events only for tags, not for branches. Same applies to branches filter, so in order to avoid actions to run on tag events we need to just specify glob for all branches (fix in this PR).Also fixed missing lint/test that got merged due to missing checks and brought back jest@29 because we can't just bump this package only: it introduces some issues in test runs (e.g. open handles appear) and has to be updated with some other packages
How has this been tested?
Release plan
Just merge
Potential risks; What to monitor; Rollback plan
No