Regenerate GitHub Action for CI with Push permission

[phuonghuynh]

@ronaldtse GitHub apply new format for its tokens, so we need to update our CI Secrets token or GHA won't work as expected

We noticed your personal access token, xxxx, has an outdated format and was used to access the GitHub API xxx

[ronaldtse]

There is no deadline for migration so we don't need to do this now.

[ronaldtse]

@phuonghuynh which repo are you seeing this? I believe relaton-ci is already using the new token format.

[phuonghuynh]

This notice is for my PAT; not CI PAT;

Last 2 GHAs failed on emit event for deploy to lambda, https://github.com/relaton/api.relaton.org/actions/runs/1221395328, so I guess that issue related to GHA CI Token; like my tested Repo Action

[ronaldtse]

@phuonghuynh What is the problem here?

I have re-generated the token, but both the old and new ones already use the new format. The token has full read/write repo/packages access:

[ronaldtse]

The secret is called RELATON_CI_PAT in all public repositories as well as in infrastructure-lambda-api. Closing this.

[phuonghuynh]

@andrew2net could we test new CI token ?

[andrew2net]

@phuonghuynh I've tried to run the manual-release workflow twice with API_VERSION: 1.9.1-preview.1 and API_VERSION: 1.9.1-preview.2, GEM_VERSION: 1.9.1 but the on-release workflow isn't triggered.

[ronaldtse]

@phuonghuynh could you please help with this task? Thanks.

[phuonghuynh]

Yes

[phuonghuynh]

@andrew2net could you help to fix GHA build failed because of rspec error?

https://github.com/relaton/api.relaton.org/runs/7592911061?check_suite_focus=true

[andrew2net]

@phuonghuynh fixed

[ronaldtse]

Ping @phuonghuynh

[phuonghuynh]

New GHA working, so I think we can close this issue, https://github.com/relaton/api.relaton.org/actions/runs/2869996420

[ronaldtse]

Thanks @phuonghuynh !