-
Notifications
You must be signed in to change notification settings - Fork 48
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
[WIP] Substrate monthly 2023 08 #1780
Open
Neopallium
wants to merge
39
commits into
frame_v2_upgrade_part2
Choose a base branch
from
substrate_monthly_2023_08
base: frame_v2_upgrade_part2
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
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
Neopallium
force-pushed
the
substrate_monthly_2023_08
branch
5 times, most recently
from
January 10, 2025 12:11
04f6d0f
to
049e0c8
Compare
Neopallium
force-pushed
the
frame_v2_upgrade_part7
branch
from
January 14, 2025 10:08
51b6934
to
cb7fbe8
Compare
Neopallium
force-pushed
the
substrate_monthly_2023_08
branch
from
January 14, 2025 10:11
049e0c8
to
8c20535
Compare
Neopallium
force-pushed
the
frame_v2_upgrade_part7
branch
from
January 14, 2025 14:22
cb7fbe8
to
5bdd573
Compare
Neopallium
force-pushed
the
substrate_monthly_2023_08
branch
from
January 14, 2025 14:23
8c20535
to
a59a88b
Compare
Neopallium
force-pushed
the
frame_v2_upgrade_part7
branch
from
January 14, 2025 15:47
5bdd573
to
7018f65
Compare
Neopallium
force-pushed
the
substrate_monthly_2023_08
branch
from
January 14, 2025 15:49
a59a88b
to
10a0049
Compare
Neopallium
force-pushed
the
frame_v2_upgrade_part7
branch
from
January 15, 2025 17:39
7018f65
to
316fceb
Compare
Neopallium
force-pushed
the
substrate_monthly_2023_08
branch
from
January 15, 2025 17:41
10a0049
to
bc774ed
Compare
Neopallium
force-pushed
the
frame_v2_upgrade_part7
branch
from
January 16, 2025 13:00
316fceb
to
a2c8e0f
Compare
Neopallium
force-pushed
the
substrate_monthly_2023_08
branch
from
January 16, 2025 13:02
bc774ed
to
fc1c422
Compare
Neopallium
force-pushed
the
frame_v2_upgrade_part7
branch
from
January 16, 2025 17:27
a2c8e0f
to
90f202f
Compare
Neopallium
force-pushed
the
substrate_monthly_2023_08
branch
2 times, most recently
from
January 16, 2025 17:32
814afd4
to
4c42555
Compare
Add 'try-runtime' feature to all pallets. Update Base pallet. Update Bridge pallet. Update Permissions pallet. Update Treasury pallet. Upgrade Group pallet. Use 'Pallet' instead of 'Module' for FRAME v1 pallets too. Add Frame v2 migration helper. Support loading chain spec with dev/testnet runtime. Add v7.0 chain spec for ci-runtime. Add CLI tool to upgrade the ci-chain. Run the integration tests before and after a chain upgrade. Bump Rust integration resource class. Update check_storage_version script for new Frame v2 version.
Update Corporate Actions pallet. Update Capital Distribution pallet. Update Corporate Ballot pallet.
Update PolymeshContracts pallet. Update NFT pallet. Updated Balances pallet. Update ComplianceManager pallet. Cargo fmt
Update Checkpoint pallet.
Update Portfolio pallet. Update Settlement pallet. Update Identity pallet.
Neopallium
force-pushed
the
frame_v2_upgrade_part7
branch
from
January 24, 2025 15:50
90f202f
to
f5bc1c0
Compare
Neopallium
force-pushed
the
substrate_monthly_2023_08
branch
from
January 24, 2025 16:01
4c42555
to
1dd79f8
Compare
Base automatically changed from
frame_v2_upgrade_part7
to
frame_v2_upgrade_part6
January 29, 2025 08:07
Base automatically changed from
frame_v2_upgrade_part6
to
frame_v2_upgrade_part5
January 29, 2025 08:08
Base automatically changed from
frame_v2_upgrade_part5
to
frame_v2_upgrade_part4
January 29, 2025 08:09
Base automatically changed from
frame_v2_upgrade_part4
to
frame_v2_upgrade_part3
January 29, 2025 08:09
Base automatically changed from
frame_v2_upgrade_part3
to
frame_v2_upgrade_part2
January 29, 2025 08:10
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.
If your PR has an external impact, please complete the
changelog
below. Headings under thechangelog
are optional, and should only be included if relevant for this PR.Please add any general description of the changes before the
changelog
.Items should be added to the
changelog
using bulletpoints.changelog
new features
[Describe the features being added in the PR]
modified external API
[List any extrinsics whose behaviour or function signature is modified]
new external API
[List any new extrinsics being introduced]
modified events
[List any events whose behaviour, name or arguments is modified]
new events
[List any new events being introduced]
other
[List any other relevant information, for example RPC function details]
data migration
[List any storage modifications required during upgrade process with details]