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

(docs): fix v1.30.0 migration guide #6596

Conversation

everettraven
Copy link
Contributor

Description of the change:

  • Fixes the v1.30.0 release migration guide. Looks like the migration template accidentally got committed and resulted in an improper migration guide being produced.

Motivation for the change:

Checklist

If the pull request includes user-facing changes, extra documentation is required:

@grokspawn
Copy link
Contributor

sanity failing because there is no docs dir in v0.19.x branch? (https://github.com/operator-framework/operator-sdk/tree/v0.19.x/doc)

@everettraven
Copy link
Contributor Author

everettraven commented Oct 11, 2023

sanity failing because there is no docs dir in v0.19.x branch? (https://github.com/operator-framework/operator-sdk/tree/v0.19.x/doc)

Ah, this looks to be because we had to drop anything > n-12 branches from the Netlify builds since we ran out of branch builds...

I'll create a separate PR to fix this because it is likely that this impacts more than just this PR.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 10, 2024
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 9, 2024
@openshift-bot
Copy link

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Mar 11, 2024
Copy link

openshift-ci bot commented Mar 11, 2024

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

missing upgrade docs for v1.30.0
3 participants