Skip to content

[epic] leverage registry+v1 composite version for bundle ordering #2479

Closed as not planned
Closed as not planned
[epic] leverage registry+v1 composite version for bundle ordering#2479
Assignees
rashmigottipati
Labels
epiclifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.v1.xIssues related to OLMv1 features that come after 1.0

Description

@grokspawn
grokspawn
opened on Feb 3, 2026

With operator-framework/api#454 and operator-framework/operator-registry#1792 merged, we can leverage on-cluster use of the composite bundle version for OLMv1.
For OLMv0, we really do not want to adjust any on-cluster behavior w.r.t. bundle succession, but we can still incorporate the information for bundle version reasoning.

Activity

  1. grokspawn
    added
    v1.xIssues related to OLMv1 features that come after 1.0
    on Feb 3, 2026
  2. joelanford
    added this to OLM v1on Feb 3, 2026
  3. grokspawn
    added
    epic
    on Feb 3, 2026
  4. grokspawn
    moved this to Implementing in OLM v1on Mar 3, 2026
  5. grokspawn
    assigned
    rashmigottipati
    on Mar 3, 2026

  6. grokspawn commented on Mar 3, 2026

    @grokspawn
    grokspawn
    on Mar 3, 2026
    ContributorAuthor

    @rashmigottipati assigned you since you pulled in a couple of these tasks

  7. rashmigottipati commented on Mar 3, 2026

    @rashmigottipati
    rashmigottipati
    on Mar 3, 2026
    Member

    @grokspawn sounds good, thanks!

  8. rashmigottipati
    linked a pull request that will close this issue✨ Add support for parsing and persisting explicit pkg.Release field #2543on Mar 6, 2026
  9. rashmigottipati
    removed a link to a pull request✨ Add support for parsing and persisting explicit pkg.Release field #2543on Mar 6, 2026

  10. github-actions commented on Jun 2, 2026

    @github-actions
    github-actionsbot
    on Jun 2, 2026 – with GitHub Actions

    Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.

  11. github-actions
    added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jun 2, 2026

  12. github-actions commented on Jul 11, 2026

    @github-actions
    github-actionsbot
    on Jul 11, 2026 – with GitHub Actions

    This issue has been closed due to inactivity.

  13. github-actions
    closed this as not plannedon Jul 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

epiclifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.v1.xIssues related to OLMv1 features that come after 1.0

Type

No type

Projects

  • OLM v1
    Status
    Implementing

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions