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

fix: resolve issues with automated releases #1974

Merged
merged 3 commits into from
Jul 20, 2022

Conversation

SgtPooki
Copy link
Member

@SgtPooki SgtPooki commented Jul 11, 2022

After enabling automated releases for this repo, I noticed a number of issues:

  1. The car file was not attached to the GitHub release notes
  2. Releases are generated for every single commit, causing release notes to become useless. We should batch commits and release only after a minimum wait time
  3. Even though semantic-release doesn't publish to npm currently (we have it disabled), the files being added to the npm tarball were unnecessary (.cache/*, and many others. You can see this on old runs). This was making the logs extremely difficult even to scroll through.
    • Specifying "files": in the package.json allows us to limit which files are included.
  4. PRs weren't testing the 'semantic-release' part of the ci.yml workflow, so everything in the ci.yml workflow could go great, and then fail during semantic-release job.
    • Now, semantic-release is run with a dry-run flag for PRs

Also, see #1970

This PR attempts to resolve all of the above issues.

@SgtPooki SgtPooki force-pushed the feat/attach-car-with-semantic-release branch from f495c4d to 1b4b31d Compare July 11, 2022 18:01
@SgtPooki SgtPooki temporarily deployed to Deploy July 11, 2022 18:05 Inactive
@SgtPooki SgtPooki marked this pull request as ready for review July 11, 2022 18:16
@SgtPooki
Copy link
Member Author

@achingbrain I was told by @BigLep that you've got a release setup where a PR is opened, and then added to as commits are merged into the main branch, and then you kick of a release just by merging that "release" PR. Is that correct?

If so, I would love to get that set up here. Can you point me in the right direction?

@SgtPooki SgtPooki force-pushed the feat/attach-car-with-semantic-release branch from 1b4b31d to 6d3e1e6 Compare July 11, 2022 18:21
@SgtPooki SgtPooki temporarily deployed to Deploy July 11, 2022 18:25 Inactive
@achingbrain
Copy link
Member

@SgtPooki - yes, libp2p and ipfs both use gated releases via release-please which it sounds like you are after - here's some example config - let me know if anything doesn't make sense.

@SgtPooki SgtPooki self-assigned this Jul 17, 2022
@SgtPooki SgtPooki requested review from hacdias and removed request for achingbrain July 18, 2022 16:44
@SgtPooki SgtPooki added P0 Critical: Tackled by core team ASAP topic/ci Continuous integration labels Jul 18, 2022
Copy link
Member

@hacdias hacdias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I also agree that this is an improvement compared to what we had, and it's also better than releasing a version with every single commit.

@SgtPooki SgtPooki merged commit 9a7cfad into main Jul 20, 2022
@SgtPooki SgtPooki deleted the feat/attach-car-with-semantic-release branch July 20, 2022 18:03
lidel added a commit that referenced this pull request Aug 9, 2022
Manual mode introduced in #1974
lidel added a commit that referenced this pull request Aug 9, 2022
* docs(readme): update translations release steps
* docs(readme): Releases are 99% automated
* docs: manual release dispatch
Manual mode introduced in #1974

Co-authored-by: Marcin Rataj <lidel@lidel.org>
ipfs-gui-bot pushed a commit that referenced this pull request Sep 9, 2022
## [2.18.0](v2.17.3...v2.18.0) (2022-09-09)

 CID `bafybeidb5eryh72zajiokdggzo7yct2d6hhcflncji5im2y5w26uuygdsm`

 ---

### Features

* IPNS Publishing ([#1973](#1973)) ([4ff4939](4ff4939))
* ux improvements to publish modal ([#1998](#1998)) ([ea4f632](ea4f632))

### Bug Fixes

* **ci:** parsing "ipfs-cluster-ctl peers ls" output ([#1966](#1966)) ([828e460](828e460))
* korean detection ([#2005](#2005)) ([362dab8](362dab8))
* Kubo agent text to link via ReleaseLink [#2010](#2010) ([#2011](#2011)) ([3d04988](3d04988))
* nodejs readme badges ([#1985](#1985)) ([a9e661b](a9e661b))
* remove web ui version and keep revision ([#2000](#2000)) ([42ed78d](42ed78d))
* resolve issues with automated releases  ([#1974](#1974)) ([9a7cfad](9a7cfad))

### Trivial Changes

* add missing classnames dependency ([#1977](#1977)) ([c4216b8](c4216b8))
* **deps:** update react-scripts ([#1969](#1969)) ([136b260](136b260))
* pull transifex translations ([#1996](#1996)) ([0de4267](0de4267))
* Pull transifex translations ([#2003](#2003)) ([cc51b15](cc51b15))
* **readme:** NodeJS version support info ([#1986](#1986)) ([829450d](829450d))
* **readme:** update release steps ([#1963](#1963)) ([c5b4822](c5b4822))
* Update .github/workflows/stale.yml [skip ci] ([f15818d](f15818d))
* update storybook and stories ([#2007](#2007)) ([83ceac1](83ceac1)), closes [/github.com/storybookjs/storybook/blob/next/MIGRATION.md#webpack-5](https://github.com/ipfs//github.com/storybookjs/storybook/blob/next/MIGRATION.md/issues/webpack-5)
@ipfs-gui-bot
Copy link
Collaborator

🎉 This PR is included in version 2.18.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P0 Critical: Tackled by core team ASAP released topic/ci Continuous integration
Projects
No open projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants