-
Notifications
You must be signed in to change notification settings - Fork 11
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
Release for v2.7.0 #784
Open
github-actions
wants to merge
2
commits into
develop
Choose a base branch
from
tagpr-from-v2.6.0
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Release for v2.7.0 #784
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
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
4 times, most recently
from
August 23, 2024 22:49
40aa2d3
to
a123db2
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
2 times, most recently
from
September 1, 2024 11:23
9783543
to
a8245cb
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
5 times, most recently
from
September 8, 2024 17:41
6495260
to
099e555
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
from
September 11, 2024 15:33
099e555
to
a51d056
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
2 times, most recently
from
September 15, 2024 08:37
a75563b
to
a64cfd1
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
from
October 1, 2024 16:37
a64cfd1
to
d6eba9a
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
from
October 1, 2024 16:39
d6eba9a
to
5246b23
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
7 times, most recently
from
October 13, 2024 13:30
2ed6f10
to
b1cec42
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
from
November 13, 2024 17:26
b1cec42
to
bbaa6d6
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
3 times, most recently
from
November 13, 2024 17:27
fb1de49
to
bd90dd6
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
3 times, most recently
from
November 28, 2024 14:46
64b00cc
to
08ac279
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
5 times, most recently
from
November 30, 2024 11:26
0b2057c
to
6829e04
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
2 times, most recently
from
December 12, 2024 18:17
3403f99
to
e6e3016
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
from
December 28, 2024 14:18
e6e3016
to
dea885a
Compare
github-actions
bot
force-pushed
the
tagpr-from-v2.6.0
branch
from
December 30, 2024 02:51
dea885a
to
04b7a5b
Compare
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.
This pull request is for the next release as v2.7.0 created by tagpr. Merging it will tag v2.7.0 to the merge commit and create a GitHub release.
You can modify this branch "tagpr-from-v2.6.0" directly before merging if you want to change the next version number or other files for the release.
How to change the next version as you like
There are two ways to do it.
What's Changed
以降
to以前
by @ChanTsune in fix: replace以降
to以前
#769melos format
by @YumNumm in executemelos format
#857New Contributors
以降
to以前
#769Full Changelog: v2.6.0...v2.7.0