Skip to content

chore(deps): update tj-actions/changed-files action to v46 #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Apr 30, 2025
Merged

chore(deps): update tj-actions/changed-files action to v46 #53

merged 1 commit into from
Apr 30, 2025

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 16, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
tj-actions/changed-files action major v45.0.6 -> v46.0.5

Release Notes

tj-actions/changed-files (tj-actions/changed-files)

v46.0.5

Compare Source

What's Changed

Full Changelog: tj-actions/changed-files@v46...v46.0.5

v46.0.4

Compare Source

What's Changed

Full Changelog: tj-actions/changed-files@v46...v46.0.4

v46.0.3

Compare Source

What's Changed

Full Changelog: tj-actions/changed-files@v46...v46.0.3

v46.0.2

Compare Source

What's Changed
New Contributors

Full Changelog: tj-actions/changed-files@v46...v46.0.2

v46.0.1

Compare Source

[!WARNING]
Security Alert: A critical security issue was identified in this action due to a compromised commit.

This commit has been removed from all tags and branches, and necessary measures have been implemented to prevent similar issues in the future.

Action Required:

  • Review your workflows executed between March 14 and March 15. If you notice unexpected output under the changed-files section, decode it using the following command: echo 'xxx' | base64 -d | base64 -d
    If the output contains sensitive information (e.g., tokens or secrets), revoke and rotate those secrets immediately.
  • If your workflows reference this commit directly by its SHA, you must update them immediately to avoid using the compromised version.
  • If you are using tagged versions (e.g., v35, v44.5.1), no action is required as these tags have been updated and are now safe to use.

Additionally, as a precaution, we recommend rotating any secrets that may have been exposed during this timeframe to ensure the continued security of your workflows.

What's Changed

Full Changelog: tj-actions/changed-files@v46...v46.0.1

v46.0.0

Compare Source

[!WARNING]
Security Alert: A critical security issue was identified in this action due to a compromised commit.

This commit has been removed from all tags and branches, and necessary measures have been implemented to prevent similar issues in the future.

Action Required:

  • Review your workflows executed between March 14 and March 15. If you notice unexpected output under the changed-files section, decode it using the following command: echo 'xxx' | base64 -d | base64 -d
    If the output contains sensitive information (e.g., tokens or secrets), revoke and rotate those secrets immediately.
  • If your workflows reference this commit directly by its SHA, you must update them immediately to avoid using the compromised version.
  • If you are using tagged versions (e.g., v35, v44.5.1), no action is required as these tags have been updated and are now safe to use.

Additionally, as a precaution, we recommend rotating any secrets that may have been exposed during this timeframe to ensure the continued security of your workflows.

What's Changed

New Contributors

Full Changelog: tj-actions/changed-files@v45.0.5...v46.0.0

What's Changed

Full Changelog: tj-actions/changed-files@v45.0.5...v46.0.0

v45.0.9

Compare Source

What's Changed

Full Changelog: tj-actions/changed-files@v45.0.4...v45.0.9

v45.0.8

Compare Source

What's Changed

Configuration

📅 Schedule: Branch creation - "before 5am on Monday,after 10pm on Monday,before 5am on Tuesday,after 10pm on Tuesday,before 5am on Wednesday,after 10pm on Wednesday,before 5am on Thursday,after 10pm on Thursday,before 5am on Friday,every weekend" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested review from a team, matchan26 and yukin01 and removed request for a team March 16, 2025 04:54
@renovate renovate bot force-pushed the renovate/major-github-actions branch 2 times, most recently from fc055a4 to 097e1e0 Compare March 23, 2025 12:44
@renovate renovate bot force-pushed the renovate/major-github-actions branch 2 times, most recently from ae9c62a to 3d47b98 Compare April 9, 2025 04:54
@renovate renovate bot force-pushed the renovate/major-github-actions branch from 3d47b98 to 70662e4 Compare April 30, 2025 08:55
@renovate renovate bot force-pushed the renovate/major-github-actions branch from 70662e4 to 2aa57a4 Compare April 30, 2025 08:59
@yukin01 yukin01 merged commit cbce7c4 into main Apr 30, 2025
2 checks passed
@yukin01 yukin01 deleted the renovate/major-github-actions branch April 30, 2025 09:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yukin01 yukin01 yukin01 approved these changes

@matchan26 matchan26 Awaiting requested review from matchan26 matchan26 was automatically assigned from globis-org/sre

Assignees

No one assigned

Labels

excluded from findy

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@yukin01