Skip to content

Bug - Build - Org and React can become out of sync resulting in build failures. #10804

Description

@dlabaj

If an update in react requires additional updates in org were a react release is required to update org we can get stuck in a scenario where we will be unable to release Patternfly react. In order to prevent this we need the ability to build and release without the need to generate and post documentation to account for these scenarios. An update needs to be added to github actions to handle this use case.


Jira Issue: PF-41

Activity

  1. added this to the Prioritized Backlog milestone on Jul 25, 2024
  2. moved this from Needs triage to Needs info in PatternFly Issueson Aug 22, 2024
  3. moved this from Needs info to Backlog in PatternFly Issueson Aug 22, 2024
  4. tlabaj commented on Aug 22, 2024

    @tlabaj
    Contributor

    Sounds like we are looking for something that will skip the docs build so we can still release.

  5. github-actions commented on Oct 23, 2024

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

  6. 1 remaining item

  7. removed this from the Prioritized Backlog milestone on Nov 21, 2024
  8. github-actions commented on Jan 23, 2025

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

  9. dlabaj commented on Feb 20, 2025

    @dlabaj
    ContributorAuthor

    This should be considered with the new api being developed using the Astro framework. I believe its not going to be an issue using the new doc core cli. We just need to verify this is true.

  10. github-actions commented on Apr 23, 2025

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

  11. github-actions commented on Sep 28, 2025

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

  12. github-actions commented on Jul 8, 2026

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions