Sourced from CasperWA/push-protected's releases.

v2.9.0

Check user (PAT) permissions

The API call to check whether a branch is protected or not has been updated, and can be done with the lowest of permission rights, however, at the same time, if the branch is protected, it is checked whether the user (PAT) has "admin" permission, since this is the only level that allows toggling review-protected branches, as well as getting the information about which checks are currently running.

The README has been updated with information about these permissions needed for certain use cases.

Furthermore, a debug parameter has been added to toggle set -x in the entrypoint.sh script. This is only intended for debugging purposes.

Changelog

v2.9.0 (2022-01-17)

Full Changelog

Implemented enhancements:

• Warn or error upon using token without proper rights #94
• Add debug option #93

Closed issues:

• Not clear which scope should I use to enable unprotect_reviews option #60

Merged pull requests:

• Check permission #95 (CasperWA)
• Update dependencies #92 (CasperWA)

* This Changelog was automatically generated by github_changelog_generator

v2.8.0

From master to main

The default branch of the repository has been changed to main. As has the the default value for the branch parameter. To keep some backwards compatibility for users who exploit that master was the default branch parameter value up to now, this is a last resort fallback value for the branch parameter, should the main branch not exist on the remote (in the target GitHub repository).

This fallback implementation also leeds to an intrinsic sanity check for whether or not the specified target branch exists on the remote (in the target GitHub repository) at all. Should this not be the case, the action will fail immediately.

IMPORTANT: If you are using master as the default branch for your repository and not defining either of the branch or ref parameters, while also having a main branch in your repository, this action will not work as you expect from this version and onwards. There is an easy fix for this, however; specify the branch parameter to be master:

name: Pushing to protected 'master' branch
uses: CasperWA/push-protected@v2
with:
  token: ${{ secrets.PUSH_TO_PROTECTED_BRANCH }}
  branch: master  # This parameter should be explicitly set, to make sure the `master` branch is the target branch.

... (truncated)

Sourced from CasperWA/push-protected's changelog.

v2.9.0 (2022-01-14)

Full Changelog

Implemented enhancements:

• Warn or error upon using token without proper rights #94
• Add debug option #93

Merged pull requests:

• Check permission #95 (CasperWA)
• Update dependencies #92 (CasperWA)

v2.8.0 (2022-01-03)

Full Changelog

Implemented enhancements:

• Update this repository's default branch to main #84
• Change default branch name to match GitHub #80

Fixed bugs:

• Force pushing tags when updating master #88
• Problem with CI #86

Merged pull requests:

• Force update master tag #89 (CasperWA)
• Fix CI runs for main updates #87 (CasperWA)
• Finish update to main with master tag #85 (CasperWA)
• Update dependencies #82 (CasperWA)
• Use main as default branch value instead of master #81 (CasperWA)

v2.7.0 (2021-12-15)

Full Changelog

Implemented enhancements:

• Consider adding ref #61

Fixed bugs:

• Finding the "previous version" for adding changelog info to release not working #77

Merged pull requests:

... (truncated)

• 5be7ea4 Release v2.9.0
• 434b9c5 Merge pull request #95 from CasperWA/check-permission
• 6369cac Update README with section on PAT user permissions
• 458b93c New debug option
• ab67aa1 Implement permissions check
• b54cd41 Update dependencies (#92)
• c2b4d13 Release v2.8.0
• 8d4040a Force update master tag (#89)
• ab78911 Remove running CI tests for pushes to 'main'
• 5667f9b Checkout correct branch for updating 'master' tag
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)