Skip to content

chore(master): release 2.4.1#400

Merged
gustavkj merged 2 commits into
masterfrom
release-please--branches--master--components--codeowners-generator
Jan 16, 2024
Merged

chore(master): release 2.4.1#400
gustavkj merged 2 commits into
masterfrom
release-please--branches--master--components--codeowners-generator

Conversation

@github-actions

@github-actions github-actions Bot commented Jan 15, 2024

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

2.4.1 (2024-01-16)

⚠ BREAKING CHANGES

  • action: Effectively change default value for preserve-block-position in github actions

Bug Fixes

  • action: Fix preserve-block-position default (#393) (f4ae6ee)
  • only include relevant files in published package (#399) (3bff598)

Miscellaneous Chores


This PR was generated with Release Please. See documentation.

@gagoar

gagoar commented Jan 15, 2024

Copy link
Copy Markdown
Owner

@gustavkj, we should avoid these when the release is from actions. The release only matches that. or we do it anyways?

@gustavkj

Copy link
Copy Markdown
Collaborator

Since changes related to the Github Action should be limited to the action.yml file, I think it should be possible to exclude commits made to that file. But I guess it would be a problem if the same commit touches other files (maybe the readme can be excluded as well).

It might also be possible to use release-please to version both the npm and action separately, but I'm not entirely sure since they are in the same directory. But I might give it a try in a test repo and see if it works as expected (related docs).

And for this PR, there is a way to specify the version manually.

@github-actions github-actions Bot changed the title chore(master): release 3.0.0 chore(master): release 2.4.1 Jan 16, 2024
@github-actions github-actions Bot force-pushed the release-please--branches--master--components--codeowners-generator branch from 79f4e09 to 86eaefd Compare January 16, 2024 09:43
@coveralls

Copy link
Copy Markdown
Collaborator

Pull Request Test Coverage Report for Build 7539739604

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 7539720404: 0.0%
Covered Lines: 266
Relevant Lines: 266

💛 - Coveralls

@codecov

codecov Bot commented Jan 16, 2024

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (10be326) 100.00% compared to head (fefdc96) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #400   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           11        11           
  Lines          287       287           
  Branches        67        67           
=========================================
  Hits           287       287           
Flag Coverage Δ
unittests 100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@gustavkj gustavkj merged commit 89183ee into master Jan 16, 2024
@gustavkj gustavkj deleted the release-please--branches--master--components--codeowners-generator branch January 16, 2024 09:46
@github-actions

Copy link
Copy Markdown
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants