Repository navigation
Tracking: prepare and manage release_v4.8.1 branch #6342
Description
This issue is to coordinate the creation and tracking of the release_v4.8.1 branch from develop.
Branch Details
- Version:
v4.8.1 - Branch to create:
release_v4.8.1 - Base branch:
develop
Tasks
- Create
release_v4.8.1branch fromdevelop - Push final PRs to
release_v4.8.1(e.g., version bump, changelog, fixes, features) - Perform QA and testing on
release_v4.8.1 - Merge
release_v4.8.1back tomasterwhen testing is complete - Tag
GreatVoyage-v4.8.1(Democritus)onmasterand release - Merge
masterback todevelop(if applicable)
Notes
- Once the
release_v4.8.1branch is created, it will act as the staging area for all final updates and fixes for this release. - Any non-release-related changes should continue in
develop.
PRs without Issue
- feat(net): optimize fetch inventory message processing logic #5895
- feat(doc): update readme for telegram groups and doc link #6364
- feat(config): sync config.conf with tron-deployment #6332
- feat(gradle): upgrade the maven publishing #6367
- fix(CheckStyle): only fix CheckStyle #6392
- feat(dependencies): update dependencies for security #6400
- refactor(crypto,api): improve code quality #6417
- fix(pb/ReasonCode): change BELOW_THAN_ME from 0X24 to 0x24 #6426
- fix(test): fix the ZksnarkInitTest #6427
- feat(dependencies): update grpc #6429
- feat(gradle): update verification metadata #6431
- fix(test): release resource of testcases gracefully #6437
- fix(test): remove all junit dir and add timeout for gRPC call #6441
- feat(version): update version to 4.8.1 #6445
- api(CodeQL): fix error message exposure in http response #6449
- feat(event): optimize event service thread close logic #6463
- test(auto-stop): prevent test hang by ensuring proper auto-stop #6469
- fix(config): remove the clearParam #6471
- fix(log): restore logger context after test to prevent pollution #6476
- feat(dependencies): bump libp2p from 2.2.6 to 2.2.7 #6481
- fix(doc): update x86 java start params #6478
- fix(testcase): rpc close leakage #6483
- fix(testcase): remove peer from PeerManager after testcase #6486
- fix(api): Optimize memory allocation for the filter interface of JSON-RPC #6495
- feat(*): disable market transaction #6499
- func(vm): optimize selfdestruct restriction #6501
- merge master to 4.8.1 #6509
- fix(doc): update readme to be more user friendly #6512
- fix(doc): remove wrong texts #6516
- fix(script): update install dependency script #6528
- fix(acurator): add more check for AssetIssueActuator #6525
- feat(event): optimize concurrent write issues for contract events #6526
- remove reduant exchange conditions #6539
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
FriendlyCM commentedon Jun 10, 2025
Hi, for the first task, we will create
release_v4.8.1branch fromdevelop.The different between
developandmastercould be find here.Is the
developbranch in a satisfactory state for the next release?If there is any problem please list here.
If no, we’re planning to create the branch in two days.
King31T commentedon Jun 10, 2025
Do final prs in task 2 mean those new prs planned to be in v4.8.1 after release_v4.8.1 is created? If not planned in v4.8.1, still merged into develop branch?
FriendlyCM commentedon Jun 10, 2025
Yep, anything that’s not going into the next release should go to develop.
GordonLtron commentedon Jun 10, 2025
The task can still be edit from develop after the states changes right? For example, a task planned to be developed in 4.8.1 but got delay; cannot meet the timeline.
FriendlyCM commentedon Jun 10, 2025
Yes, if the feature isn’t ready, it won’t be merged into the release branch. It should go back to the issue pool and wait for a future release.
FriendlyCM commentedon Jun 12, 2025
If there are no further questions, the
release_v4.8.1branch will be created this afternoon.Please raise any objections as soon as possible.
jwrct commentedon Jun 12, 2025
Does this version already have a rough timeline?
FriendlyCM commentedon Jun 12, 2025
The development cycle for this version is tentatively set for June to August. We can tracking the development here .
If needed, we can adjust this timeline.
lxcmyf commentedon Jun 12, 2025
@troncommons
Is there any significant update worth looking forward to in this version?
22 remaining items