Skip to content

chore: disable unauthorized file change check due to known vulnerabilities #1622

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.

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

Merged
merged 1 commit into from
Apr 23, 2025

Conversation

aialok
Copy link
Member

@aialok aialok commented Apr 16, 2025

What kind of change does this PR introduce?
Chore / Security Patch

Issue Number:

Screenshots/videos:

If relevant, did you update the documentation?

Summary
Temporarily disables the check for unauthorized file changes in the GitHub Actions workflow due to known security vulnerabilities. This is a precautionary measure until a safer implementation is available.

Does this PR introduce a breaking change?

No

Checklist

Please ensure the following tasks are completed before submitting this pull request.

@aialok aialok requested a review from a team as a code owner April 16, 2025 14:17
@aialok
Copy link
Member Author

aialok commented Apr 19, 2025

@DarhkVoyd @benjagm Can you please review this PR?

Copy link
Member

@DarhkVoyd DarhkVoyd left a comment

Choose a reason for hiding this comment

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

Since this GitHub action has a history of vulnerabilities, commenting it makes sense to keep a record of the tracked files until we find an alternative and quickly re-enable our actions and pipeline. We should permanently migrate away from it as a dependency and remove this job. We should create an issue to replace it with an alternative. We can also link the resource to help new contributors.

@benjagm benjagm merged commit 2c0b8d8 into json-schema-org:main Apr 23, 2025
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.

3 participants