Skip to content

fix(ci): Use correct READ_ONLY access value instead of READ #7239

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

Merged
nuugen merged 1 commit into from
Mar 6, 2025
Merged

fix(ci): Use correct READ_ONLY access value instead of READ #7239

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion catalog-info.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -363,4 +363,4 @@ spec:
release-eng:
access_level: BUILD_AND_READ
everyone:
access_level: READ
access_level: READ_ONLY
Copy link
Copy Markdown
Member

@v1v v1v Mar 6, 2025

Choose a reason for hiding this comment

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

I think I took the above access level called BUILD_AND_READ and removed BUILD_AND, assuming it was enough :/ . It's undoubtedly misleading that _ONLY is needed; what else will be read if it's only read? Thanks for the fix Linh!