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

archive(1.3) isolation: remove all other versions, pt 2: reviewable #4485

Open
wants to merge 12 commits into
base: unsupported/1.3
Choose a base branch
from

Conversation

pepopowitz
Copy link
Collaborator

@pepopowitz pepopowitz commented Oct 17, 2024

Part of #2189.

Note: this PR will be merged into the unsupported/1.3 branch. It will never make it into main.

Description

Continues the process of archival/isolation for version 1.3. Many of the steps were done by a computer for me (the src/hacks/isolateVersion script), but the last few are manual:

Progress

  • exclude all other versions from the main version file
  • exclude all other versions from the optimize version file
  • prevent unsupported site from being crawled
  • fix Dockerfile for local debugging
  • update theme components
  • update CI workflows
  • update docusaurus config
  • configure Optimize docs instance
  • fix incorrect URLs
  • update rewrite rules based on 1.3 basepath
  • figure out how to fix the broken links on the homepage (many link to nonexistent pages in this version)
  • figure out if I need to fix the links reported by vale

When should this change go live?

  • This is a bug fix, security concern, or something that needs urgent release support.
  • This is already available but undocumented and should be released within a week.
  • This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
  • This is part of a scheduled alpha or minor. (apply alpha or minor label)
  • There is no urgency with this change and can be released at any time.

PR Checklist

  • My changes are for an already released minor and are in /versioned_docs directory.
  • My changes are for the next minor and are in /docs directory (aka /next/).

@pepopowitz pepopowitz self-assigned this Oct 17, 2024
@@ -282,7 +282,7 @@

<div bpmn="best-practices/creating-readable-process-models-assets/retry-anti-pattern.bpmn" thumbs="down" />

All operations use cases put into the model can be handled via Camunda tooling, e.g. by [retrying](/docs/components/concepts/job-workers/#completing-or-failing-jobs) or [Camunda Operate](/docs/components/operate/operate-introduction/).
All operations use cases put into the model can be handled via Camunda tooling, e.g. by [retrying](/docs/components/concepts/job-workers/#completing-or-failing-jobs) or [Camunda Operate](/docs/components/operate/).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[docsInstance.hrefDocsToDocs] Improper link format: 'Camunda Operate'. Please specify the file extension.

@pepopowitz pepopowitz marked this pull request as ready for review October 21, 2024 17:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 👀 In Review
Development

Successfully merging this pull request may close these issues.

1 participant