Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Feat/polkadot v1.3.0 uplift #1207

Merged
merged 21 commits into from
Apr 24, 2024
Merged

Feat/polkadot v1.3.0 uplift #1207

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
7539bf6
Init commit
Dinonard Mar 26, 2024
be03b55
Further modifications
Dinonard Mar 27, 2024
18b99eb
Further cleanup
Dinonard Mar 27, 2024
54c9199
Migrations & benchmark fixes
Dinonard Mar 27, 2024
501d04b
Fix tests & compilation issues
Dinonard Mar 27, 2024
58b46c2
Eth debug RPC
Dinonard Mar 27, 2024
307e9e1
Remove todos
Dinonard Mar 27, 2024
55893a9
TODOs
Dinonard Mar 27, 2024
d2e43fb
Fixes
Dinonard Mar 27, 2024
79faabe
Change dep back
Dinonard Mar 27, 2024
0f944ac
Remove double debug server
Dinonard Mar 27, 2024
2bc3b67
Linting
Dinonard Mar 27, 2024
a011505
Cleanup
Dinonard Mar 28, 2024
d1d3cc7
Coverage CI change
Dinonard Mar 29, 2024
f2b8269
Fixes
Dinonard Mar 29, 2024
1f776e9
Merge remote-tracking branch 'origin/master' into feat/polkadot-v1.3.…
Dinonard Apr 4, 2024
0e57cc6
Post-merge fixes
Dinonard Apr 4, 2024
bce3a5c
Comments
Dinonard Apr 15, 2024
616af3f
Remove dead code
Dinonard Apr 15, 2024
d109521
Merge remote-tracking branch 'origin/master' into feat/polkadot-v1.3.…
Dinonard Apr 23, 2024
b427753
Remove unused import
Dinonard Apr 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,10 +60,6 @@ All branch names should adhere to the following rules:
- `doc/*`: documentation changes
- `fix/*`: bug fixes


**TODO**: We don't really use this at all from what I've seen?
- `development/*`: nodes that are actively in development (including release candidates) will have the `development/` prefix in their branch name.

Every major feature will be first deployed on our testnet parachain _Shibuya_ after which it can be deployed on one of the production networks.
The expected flow is:

Expand Down
Loading
Loading