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

Ensure that links to release artifacts are up2date #4908

Open
MaxTru opened this issue Jan 29, 2025 · 2 comments
Open

Ensure that links to release artifacts are up2date #4908

MaxTru opened this issue Jan 29, 2025 · 2 comments

Comments

@MaxTru
Copy link
Contributor

MaxTru commented Jan 29, 2025

Description

Ensure that links to release artifacts are up2date

Reproduce

(As of 29.01.2025)

  1. Open https://docs.camunda.io/docs/self-managed/setup/deploy/local/c8run/#install-and-start-camunda-8-run. See Download the [latest release of Camunda 8 Run](https://github.com/camunda/camunda/releases/tag/8.6.6) for your operating system and architecture. Opening the .tgz file extracts the Camunda 8 Run script into a new directory.
  2. See it points to https://github.com/camunda/camunda/releases/tag/8.6.6
  3. It should point to https://github.com/camunda/camunda/releases/tag/8.6.7

Expected behavior

Link should point to latest patch level of the currently selected "branch"

Additional context

Discussed with @akeller in person

@akeller
Copy link
Member

akeller commented Jan 29, 2025

We can add this to the docs release manager responsibilities if this is something that happens monthly. Not a smart solution, but predictable.

@MaxTru
Copy link
Contributor Author

MaxTru commented Jan 29, 2025

Hi @akeller - just discussed with @kellervater . Infra Team has a similar problem and they have a solution for this in place using renovate. Probably it would help if you open an #ask-infra request and ask them to potentially re-use their solution sketch.

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

No branches or pull requests

2 participants