feat: update README.md to trigger release #1425
Merged
Conversation
This file contains 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
kangmingtay
approved these changes
Feb 14, 2024
J0
pushed a commit
that referenced
this pull request
Feb 14, 2024
🤖 I have created a release *beep* *boop* --- ## [2.142.0](v2.141.0...v2.142.0) (2024-02-14) ### Features * alter tag to use raw ([#1427](#1427)) ([53cfe5d](53cfe5d)) * update README.md to trigger release ([#1425](#1425)) ([91e0e24](91e0e24)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
uxodb
pushed a commit
to uxodb/auth
that referenced
this pull request
Nov 13, 2024
## What kind of change does this PR introduce? It seems like in v2.141.0 `release-please` succeeded but there was a [likely transient](https://github.com/supabase/gotrue/actions/runs/7889273761/job/21528885508#step:7:30) failure in the build. It seems like release-please needs to run before an image can be published. However, since release please has completed for v2.141.0 it's not possible to publish an image again since `release-please` re-runs of v2.141.0 will lead to early termination since v2.141.0 has already been published. We publish a new version to get around this. These are some README changes to trigger the publication of a new version Co-authored-by: joel <joel@joels-MacBook-Pro.local>
uxodb
pushed a commit
to uxodb/auth
that referenced
this pull request
Nov 13, 2024
🤖 I have created a release *beep* *boop* --- ## [2.142.0](supabase/auth@v2.141.0...v2.142.0) (2024-02-14) ### Features * alter tag to use raw ([supabase#1427](supabase#1427)) ([53cfe5d](supabase@53cfe5d)) * update README.md to trigger release ([supabase#1425](supabase#1425)) ([91e0e24](supabase@91e0e24)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
LashaJini
pushed a commit
to LashaJini/auth
that referenced
this pull request
Nov 13, 2024
## What kind of change does this PR introduce? It seems like in v2.141.0 `release-please` succeeded but there was a [likely transient](https://github.com/supabase/gotrue/actions/runs/7889273761/job/21528885508#step:7:30) failure in the build. It seems like release-please needs to run before an image can be published. However, since release please has completed for v2.141.0 it's not possible to publish an image again since `release-please` re-runs of v2.141.0 will lead to early termination since v2.141.0 has already been published. We publish a new version to get around this. These are some README changes to trigger the publication of a new version Co-authored-by: joel <joel@joels-MacBook-Pro.local>
LashaJini
pushed a commit
to LashaJini/auth
that referenced
this pull request
Nov 13, 2024
🤖 I have created a release *beep* *boop* --- ## [2.142.0](supabase/auth@v2.141.0...v2.142.0) (2024-02-14) ### Features * alter tag to use raw ([supabase#1427](supabase#1427)) ([53cfe5d](supabase@53cfe5d)) * update README.md to trigger release ([supabase#1425](supabase#1425)) ([91e0e24](supabase@91e0e24)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
LashaJini
pushed a commit
to LashaJini/auth
that referenced
this pull request
Nov 15, 2024
## What kind of change does this PR introduce? It seems like in v2.141.0 `release-please` succeeded but there was a [likely transient](https://github.com/supabase/gotrue/actions/runs/7889273761/job/21528885508#step:7:30) failure in the build. It seems like release-please needs to run before an image can be published. However, since release please has completed for v2.141.0 it's not possible to publish an image again since `release-please` re-runs of v2.141.0 will lead to early termination since v2.141.0 has already been published. We publish a new version to get around this. These are some README changes to trigger the publication of a new version Co-authored-by: joel <joel@joels-MacBook-Pro.local>
LashaJini
pushed a commit
to LashaJini/auth
that referenced
this pull request
Nov 15, 2024
🤖 I have created a release *beep* *boop* --- ## [2.142.0](supabase/auth@v2.141.0...v2.142.0) (2024-02-14) ### Features * alter tag to use raw ([supabase#1427](supabase#1427)) ([53cfe5d](supabase@53cfe5d)) * update README.md to trigger release ([supabase#1425](supabase#1425)) ([91e0e24](supabase@91e0e24)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce?
It seems like in v2.141.0
release-pleasesucceeded but there was a likely transient failure in the build.It seems like release-please needs to run before an image can be published. However, since release please has completed for v2.141.0 it's not possible to publish an image again since
release-pleasere-runs of v2.141.0 will lead to early termination since v2.141.0 has already been published.We publish a new version to get around this. These are some README changes to trigger the publication of a new version