Skip to content

chore(ci): fix release workflow permission #2110

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
Feb 20, 2024
Merged

Conversation

dreamorosi
Copy link
Contributor

@dreamorosi dreamorosi commented Feb 20, 2024

Description of your changes

This PR adds a new contents:read permission the two jobs that call the lambda layer publish reusable workflows.

Related issues, RFCs

Issue number: #2111

Checklist

  • My changes meet the tenets criteria
  • I have performed a self-review of my own code
  • I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my change is effective and works
  • The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

  • I have documented the migration process
  • I have added, implemented necessary warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

@dreamorosi dreamorosi self-assigned this Feb 20, 2024
@dreamorosi dreamorosi requested a review from a team February 20, 2024 13:48
@dreamorosi dreamorosi requested a review from a team as a code owner February 20, 2024 13:48
@boring-cyborg boring-cyborg bot added the automation This item relates to automation label Feb 20, 2024
@pull-request-size pull-request-size bot added the size/XS PR between 0-9 LOC label Feb 20, 2024
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

This comment was marked as resolved.

@github-actions github-actions bot added do-not-merge This item should not be merged need-issue This PR needs an issue before it can be reviewed/worked on further labels Feb 20, 2024
@dreamorosi dreamorosi removed do-not-merge This item should not be merged need-issue This PR needs an issue before it can be reviewed/worked on further labels Feb 20, 2024
@dreamorosi dreamorosi merged commit e8915a0 into main Feb 20, 2024
@dreamorosi dreamorosi deleted the chore/make-release-fixes branch February 20, 2024 13:53
@dreamorosi dreamorosi linked an issue Feb 20, 2024 that may be closed by this pull request
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation This item relates to automation size/XS PR between 0-9 LOC
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Maintenance: fix release workflow
2 participants