Skip to content

Commit

Permalink
update
Browse files Browse the repository at this point in the history
  • Loading branch information
stevensJourney committed Oct 12, 2023
1 parent a005ce2 commit 93ec478
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 11 deletions.
1 change: 1 addition & 0 deletions .github/workflows/build-packages.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ jobs:
steps:
- uses: actions/checkout@v4
with:
submodules: true
persist-credentials: false

- name: Setup NodeJS
Expand Down
12 changes: 2 additions & 10 deletions .github/workflows/dev-packages.yaml
Original file line number Diff line number Diff line change
@@ -1,16 +1,8 @@
# Action to publish packages under the `next` tag for testing
# Packages are versioned as `0.0.0-dev.{short-sha}`
# Submodule packages are versioned by default, but can be disabled
# if using a package from the external submodule repo.
name: Packages Deploy

on:
workflow_dispatch:
inputs:
include_submodules:
type: boolean
description: Dev version submodule packages?
default: true
on: workflow_dispatch

jobs:
publish:
Expand All @@ -19,7 +11,7 @@ jobs:
steps:
- uses: actions/checkout@v4
with:
submodules: ${{ github.event.inputs.include_submodules }}
submodules: true
persist-credentials: false

- name: Setup NodeJS
Expand Down
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,11 +42,13 @@ yarn build:packages


### Development Packages
Development packages can be published by manually triggering the `dev-packages` workflow. Development packages are versioned as `0.0.0-dev.{short-sha}`. Submodule packages are checked out, versioned and published by default, but this can be disabled if using submodule packages which are published from it's own repository.
Development packages can be published by manually triggering the `dev-packages` workflow. Development packages are versioned as `0.0.0-dev.{short-sha}`.

### Production Packages
Packages should be versioned with Lerna after PR approval.

Submodule production packages should be versioned, tagged and published from their own repository. Any dependencies should be updated here (if applicable) before versioning local packages.

```bash
lerna version --no-private
```
Expand Down

0 comments on commit 93ec478

Please sign in to comment.