Skip to content

Fix javadoc publish by switching from PAT to deploy key#268

Merged
merlimat merged 1 commit intooxia-db:mainfrom
merlimat:fix-javadoc-deploy
Mar 16, 2026
Merged

Fix javadoc publish by switching from PAT to deploy key#268
merlimat merged 1 commit intooxia-db:mainfrom
merlimat:fix-javadoc-deploy

Conversation

@merlimat
Copy link
Collaborator

Summary

  • The PAGES_DEPLOY_TOKEN (personal access token) used to publish javadocs to oxia-db.github.io was expired/invalid
  • Switch to a deploy key (PAGES_DEPLOY_KEY) which is scoped to the target repo and doesn't expire
  • Deploy key has already been configured on both repos

Test plan

  • Merge and verify the javadoc publish workflow succeeds on next main push

The personal access token (PAGES_DEPLOY_TOKEN) was expired/invalid,
causing the push to oxia-db.github.io to fail. Switch to a deploy
key (PAGES_DEPLOY_KEY) which is scoped to the target repo and does
not expire.

Signed-off-by: Matteo Merli <mmerli@apache.org>
@merlimat merlimat merged commit 3ecb1c5 into oxia-db:main Mar 16, 2026
2 checks passed
@merlimat merlimat deleted the fix-javadoc-deploy branch March 16, 2026 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant