-
Notifications
You must be signed in to change notification settings - Fork 661
chore: update to v12 beta 6 #2524
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
Merged
Merged
Changes from all commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
aae925f
chore: add a github action for publishing lerna from-package (#2518)
maribethb 8c1278e
chore: fix workflow name
maribethb 962e6a7
fix: Fix clean:node script
cpcallen d83ea84
chore(deps): Update blockly to v12.0.0-beta.4
cpcallen 20ab15a
fix(FieldColour): Fix type of FieldColour.prototype.isFullBlockField
cpcallen 55e188c
fix(FieldMultilineInput): Use string literal instead of Field.NBSP
cpcallen bf2878c
fix(FieldGridDropdown): Fix type error caused by separators
cpcallen 78badf5
chore(deps): Update blockly to v12.0.0-beta.5
cpcallen 6e9d3fe
fix(fields): Implement getClass method
cpcallen 43bdfab
fix(FieldGridDropdown): Handle presence of HTMLElement in MenuOptions
cpcallen 1d80511
chore: Update to v12 beta 6.
gonfunko 452051e
fix: Fix the field-grid-dropdown tests.
gonfunko 6bd3916
fix: Fix shadow-block-converter tests.
gonfunko bf44961
fix: Remove use of deleted `Block.setEnabled()`.
gonfunko a060be7
Revert "fix(fields): Implement getClass method"
gonfunko 144b6d0
Revert "fix: Add `getClass()` to `FieldColour`. (#2506)"
gonfunko 8370d9c
chore: skip shadow block tests that need jsdom work
maribethb 9dc3124
chore: try updating the package-lock, unskip tests
maribethb 539ae4f
revert: "fix(FieldMultilineInput): Use string literal instead of Fiel…
maribethb 49d9d11
chore: skip shadow block converter tests
maribethb ad8ce93
chore: Merge branch 'master' into beta7
maribethb File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,71 @@ | ||
| # This workflow can be manually triggered to publish all of the plugins | ||
| # that have a version in their package.json that is newer than what | ||
| # is available in the npm registry. This is useful if lerna publishing | ||
| # failed after a package had its version updated on github but before | ||
| # that version was published to npm. | ||
|
|
||
| name: publish unpublished plugins | ||
|
|
||
| on: | ||
| workflow_dispatch: # Manually trigger. Colon is required. | ||
|
|
||
| permissions: | ||
| contents: write # For checkout and tag. | ||
| packages: write # For publish. | ||
|
|
||
| jobs: | ||
| publish: | ||
| runs-on: ubuntu-latest | ||
| # Don't try to publish from a fork of google/blockly-samples. | ||
| if: ${{ github.repository_owner == 'google' }} | ||
|
|
||
| # Environment specific to releasing so we can isolate the npm token. | ||
| environment: release | ||
|
|
||
| steps: | ||
| - name: Checkout | ||
| uses: actions/checkout@v3 | ||
| # fetch all tags and commits so that lerna can version appropriately | ||
| with: | ||
| fetch-depth: 0 | ||
| ref: 'master' | ||
|
|
||
| # This uses a reverse-engineered email for the github actions bot. See | ||
| # https://github.com/actions/checkout/issues/13#issuecomment-724415212 | ||
| - name: Git Identity | ||
| run: | | ||
| git config --global user.name 'github-actions[bot]' | ||
| git config --global user.email '<41898282+github-actions[bot]@users.noreply.github.com' | ||
|
|
||
| - name: Setup Node | ||
| uses: actions/setup-node@v3 | ||
| with: | ||
| node-version: 20 | ||
|
|
||
| - name: Configure npm | ||
| run: npm config set //wombat-dressing-room.appspot.com/:_authToken=$NODE_AUTH_TOKEN | ||
| env: | ||
| NODE_AUTH_TOKEN: ${{ secrets.RELEASE_BACKED_NPM_TOKEN }} | ||
|
|
||
| - name: NPM install | ||
| # Use CI so that we don't update dependencies in this step. | ||
| run: npm ci | ||
|
|
||
| - name: Build | ||
| run: npm run build | ||
|
|
||
| - name: Test | ||
| run: npm run test | ||
|
|
||
| - name: Publish from-package | ||
| env: | ||
| GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| run: cd plugins && npx lerna publish from-package --yes | ||
|
|
||
| update-gh-pages: | ||
| name: Update GitHub Pages | ||
| # Call the Update gh-pages workflow only if publishing succeeds | ||
| needs: [publish] | ||
| # Don't try to auto-update if on a fork of google/blockly-samples. | ||
| if: ${{ github.repository_owner == 'google' }} | ||
| uses: ./.github/workflows/update_gh_pages.yml | ||
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For consistency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was done from merging in master, I don't want to muddy up actual changes into what should be a merge commit. Anyway, the publish action was already lower case so it's not really any more inconsistent than publish already is