Skip to content
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

CI: dependabot can't push to docker registry #705

Closed
qkaiser opened this issue Jan 16, 2024 · 2 comments
Closed

CI: dependabot can't push to docker registry #705

qkaiser opened this issue Jan 16, 2024 · 2 comments
Labels
automated bug Something isn't working

Comments

@qkaiser
Copy link
Contributor

qkaiser commented Jan 16, 2024

If you take a look at #703, you'll see that the docker container build fails because we receive a 403 when trying to push to the registry.

It's due to the way Github set permissions. If a pull request is created by a member that's not part ot the organization, then it should not have a token with write access permissions to the repo and registries.

There is detailed documentation about this here:

We should adapt our Github workflow so that trusted users like Github dependabot can work.

@qkaiser qkaiser added bug Something isn't working automated labels Jan 16, 2024
@qkaiser
Copy link
Contributor Author

qkaiser commented Jan 16, 2024

Once this is taken care of, we can define a dependabot configuration file at https://github.com/onekey-sec/unblob/network/updates so that we receive weekly updates for dependencies.

@qkaiser
Copy link
Contributor Author

qkaiser commented Jan 22, 2024

Fixed by #708

@qkaiser qkaiser closed this as completed Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant