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.

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

Update Substrate deps to 0.9.33 #146

Merged
merged 52 commits into from
Jan 5, 2024
Merged

Update Substrate deps to 0.9.33 #146

merged 52 commits into from
Jan 5, 2024

Conversation

rakanalh
Copy link
Contributor

@rakanalh rakanalh commented Nov 16, 2023

Changes include:

  • Update cere and cere-dev spec & transaction versions
  • Upgrade substrate deps to 0.9.33
  • Fix issues related to upgrade
  • Increment node version to 4.8.4
  • Updated changelog

MERGE #173 BEFORE THIS ONE.

@rakanalh rakanalh changed the base branch from dev to feature/substrate-0.9.32 November 16, 2023 14:38
@rakanalh rakanalh changed the base branch from feature/substrate-0.9.32 to dev November 22, 2023 09:06
@rakanalh rakanalh self-assigned this Nov 22, 2023
@rakanalh rakanalh marked this pull request as ready for review November 22, 2023 16:34
This was referenced Nov 27, 2023
rakanalh added a commit that referenced this pull request Nov 29, 2023
This is a PR that should precede #146 to be able to tag this 4.8.2
release prior to merging the 0.9.33 PR.

- [x] Change version to 4.8.2
- [x] Update spec and transaction versions
  - [x] Update cere-dev
  - [x] Update cere
Copy link

gitguardian bot commented Dec 29, 2023

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id Secret Commit Filename
9100662 Generic High Entropy Secret a861c5b node/service/chain-specs/example.json View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

@rakanalh rakanalh merged commit 83edd7d into dev Jan 5, 2024
5 of 6 checks passed
@rakanalh rakanalh deleted the feature/substrate-0.9.33 branch January 5, 2024 22:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants