Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

actions/deploy: bump nais/setup to v1.0.3 to avoid GitHub API rate limit

Closed Beginner friendly
#372 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, go, yaml
Domain
ci-cd, devops

Research direction

Find the v3 composite action definition that calls nais/[email protected]; the issue identifies this action and the team and environment inputs. Read the workflow action definition, then update its setup version to v1.0.3 or newer. Done when the v3 action uses a release with the github-token input that defaults to github.token.

Written by the indexing model from the issue text.

Description

nais/deploy/actions/deploy@v3 calls nais/[email protected]. That version fetches the nais CLI release info from the GitHub API without authentication, so deploys fail intermittently on shared GitHub-hosted runners:

NaisCliError: Failed to fetch release information: API rate limit exceeded for <runner IP>.
❌ Failed to setup nais CLI

Callers can't work around it: the composite action passes only team and environment to nais/setup, and v1.0.0-next.7 has no token input.

nais/setup v1.0.3 adds a github-token input that defaults to github.token, which fixes this. Could actions/deploy in v3 be bumped to nais/setup ≥ v1.0.3?

Seen several times on 13 October 2026 in navikt/copilot, on "Deploy PR to dev" jobs.

Dominant language
Go
Stars
3
Forks
9
Avg merge
2m
Merged PRs (30d)
2

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nais/deploy

All issues in nais/deploy

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.