Skip to content
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

ci(release-please): pin action version and allow manually running action #7222

Merged
merged 1 commit into from
Jun 26, 2023

Conversation

benelan
Copy link
Member

@benelan benelan commented Jun 26, 2023

Related Issue: #

Summary

The release-please action randomly started failing 3 days ago with this unhelpful error. It looks like they released 3 days ago, so I'm pinning the version to the one before that and hoping it will fix it.

I also added the workflow_dispatch trigger so we can run the action manually.

@benelan benelan requested a review from a team as a code owner June 26, 2023 21:58
@github-actions github-actions bot added the chore Issues with changes that don't modify src or test files. label Jun 26, 2023
@benelan
Copy link
Member Author

benelan commented Jun 26, 2023

I'm gonna go ahead and push this thru cuz I need to see if it fixes the issue and continue troubleshooting if it doesn't. cc @jcfranco

@benelan benelan added the skip visual snapshots Pull requests that do not need visual regression testing. label Jun 26, 2023
@benelan benelan merged commit 311e3b5 into master Jun 26, 2023
@benelan benelan deleted the benelan/release-please-troubleshooting branch June 26, 2023 22:30
@github-actions github-actions bot added this to the 2023 June patch priorities milestone Jun 26, 2023
benelan added a commit that referenced this pull request Jun 26, 2023
**Related Issue:** #7222

## Summary
Pinning the `release-please` Github Action version in the PR above fixed
the error, so their release must have broken something for us.
`release-please` is trying to release `v1.5.0` instead of `v1.4.3`
because we installed a feat and subsequently reverted it, but our
current version is still `1.5.0-next.5`.

[The
logs](https://github.com/Esri/calcite-components/actions/runs/5383995298/jobs/9771404018#step:2:102)
say it's skipping the conventional commit versioning strategy and
forcing `1.5.0`. I'm hoping I can force `1.4.3` instead, as described in
their [manifest
doc](https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md#configfile).
If this doesn't work I may need to change the package.json versions back
to `1.4.3-next.7`.
benelan added a commit that referenced this pull request Jun 27, 2023
…issue-template-checkbox

* origin/master: (32 commits)
  ci: double build cc when publishing to workaround stencil types bug (#7227)
  build: bump package versions back to 1.5.0-next.5 (#7228)
  chore: release latest (#7144)
  ci: hardcode release version due to reverting feat (#7225)
  fix(tree-item): ensure expanded tree-item is displayed when expanded and made visible (#7216)
  ci(release-please): pin action version and allow manually running action (#7222)
  fix(input, input-number): allows numeric characters. (#7213)
  build(t9n): generate json file containing t9n values (#7214)
  chore: release next
  fix(combobox, dropdown, input-date-picker, input-time-picker, popover, tooltip): Prevent repositioning from affecting other floating components (#7178)
  build: update browserslist db (#7192)
  build: ignore node_modules and build outputs when watching for changes during stencil tests (#7209)
  test: set up `disabled` helper to run a test per use case (#7089)
  ci: set design complete label conditionals (#7206)
  chore: release next
  fix(list): update selectedItems property on all item selection changes (#7204)
  chore: fix sorting logic for t9nmanifest entries (#7203)
  fix(radio-button):  focuses first focusable radio-button element in group. (#7152)
  chore: release next
  fix(alert): update alert queue when an alert is removed from the DOM (#7189)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Issues with changes that don't modify src or test files. skip visual snapshots Pull requests that do not need visual regression testing.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant