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

📖 Deploy most recent release documentation as 'latest' alias #3102

Merged
merged 1 commit into from
Mar 30, 2024

Conversation

embik
Copy link
Member

@embik embik commented Mar 27, 2024

Summary

I noticed that on https://docs.kcp.io, the "default" release (the release you get when going to https://docs.kcp.io/kcp/) points to 0.11. The reason for that is that the "default" release was set at some point manually, but it was never automated.

This PR:

  • tries to figure out if the pipeline is running for the latest released version series (e.g. v0.23 at the moment)
  • if so, updates a version alias "latest" to the version while deploying
  • ensures that the default version points to the "latest" alias

Related issue(s)

Fixes #

Release Notes

NONE

@kcp-ci-bot kcp-ci-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has signed the DCO. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Mar 27, 2024
@embik
Copy link
Member Author

embik commented Mar 27, 2024

I suppose the latest version detection doesn't work (yet) in the GitHub action. Will work on it.

Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
@embik embik force-pushed the add-latest-docs-alias branch from a1133a3 to 60ea4f3 Compare March 28, 2024 13:26
@embik
Copy link
Member Author

embik commented Mar 28, 2024

This should be ready for review now.

@embik
Copy link
Member Author

embik commented Mar 28, 2024

/cc @xrstf

@kcp-ci-bot kcp-ci-bot requested a review from xrstf March 28, 2024 13:30
@sttts
Copy link
Member

sttts commented Mar 28, 2024

/approve

@kcp-ci-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sttts

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kcp-ci-bot kcp-ci-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 28, 2024
@mjudeikis
Copy link
Contributor

/lgtm

@kcp-ci-bot kcp-ci-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 30, 2024
@kcp-ci-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 4bcc0ddaaf0c628e0c669bc4989d2324e4a7c384

@kcp-ci-bot kcp-ci-bot merged commit 47001af into kcp-dev:main Mar 30, 2024
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants