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

Automated release pipeline #20

Merged
merged 5 commits into from
Feb 23, 2024
Merged

Automated release pipeline #20

merged 5 commits into from
Feb 23, 2024

Conversation

leordev
Copy link
Member

@leordev leordev commented Feb 23, 2024

  • Add a release workflow.
  • Release instructions added on the README file.

Working Evidence: https://github.com/TBD54566975/web5-swift/releases/tag/0.0.3-test (let's remove it before merging it!)

@leordev leordev force-pushed the leordev/autoreleases branch 3 times, most recently from c437a6b to cbd190a Compare February 23, 2024 20:15
@leordev leordev marked this pull request as ready for review February 23, 2024 20:55
@leordev leordev changed the title automated release bump wip Automated release bump Feb 23, 2024
@leordev leordev changed the title Automated release bump Automated release pipeline Feb 23, 2024
Copy link
Contributor

@amika-sq amika-sq left a comment

Choose a reason for hiding this comment

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

Looks great! Just one minor comment, not blocking at all though.

- name: Checkout code
uses: actions/checkout@v4
with:
fetch-depth: 100
Copy link
Contributor

Choose a reason for hiding this comment

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

Curious if we can/should reduce this. Would we be able to get away with 1 here?

Copy link
Member Author

Choose a reason for hiding this comment

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

I did a little research and I think the best we can get away with is by using filter: tree:0:
actions/checkout#1152 (comment)

The reason is that we need the history to be able to figure out the latest git tag. A shallow clone unfortunately does not give us that.

Maybe we can reduce the depth to 50, or 25 assuming that we will always cut new releases when we are about 50 or 25 merged PRs. WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

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

Gotcha! I think it's fine to leave at 100 then, as that should usually contain the last tag. Probably a bit better to overestimate than under :)

@leordev leordev merged commit 28b3c86 into main Feb 23, 2024
5 checks passed
@leordev leordev deleted the leordev/autoreleases branch February 23, 2024 21:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants