Skip to content

Set up Felt React development branch and prerelease workflow #12666

Description

@patternfly-jira-sync
  • Create/configure the React felt-v1 branch.

  • Establish React package prerelease publishing.

“How to” docs modified from

To set up a development branch in react

  • Create the new major release development branch

  • Open a PR against the release development branch

  • In each react package’s package.json

  • Change the version to 0.0.1-prerelease.0

  • update the publishConfig ‘tag’ to ‘prerelease’ and add ‘access: “public”’

  • Update all @patternfly dependencies to use the new versions

  • In .github/workflows/release.yml

  • Update on: push: branches: felt-v1

  • In release.sh

  • Update the lerna publish command in release.sh to add

  • yarn run lerna publish prerelease --preid=prerelease --dist-tag=prerelease --yes 2>&1 | tee lerna-output.txt

  • # use lerna command below for dry run

  • # yarn run lerna version prerelease --preid=prerelease --dist-tag=prerelease --yes --no-git-tag-version --no-push | tee lerna-output.txt

  • update lerna.json to include ‘allowbranch: [‘main’, ‘felt-v1’]’

  • It should always include all branches that are releasing different major versions

  • Note: this PR will fail to build because it’ll try to build with the old github actions. You need to merge it for PRs on this branch to build.

  • Also need to: 

  • set up workspace (standing surge site for previewing what’s on the development branch)

  • In org add to docs-framework package.json

"publishConfig": {

   "access": "public",

   "tag": "prerelease"

},


Jira Issue: PF-4694

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions