-
Notifications
You must be signed in to change notification settings - Fork 7
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
Feat: Upgrade parachain 1.21.0 #61
Conversation
… testnet, and local testnet running parachain 1.21.0. Fixed compile errors after is/asV1019000 was automatically removed by typegen.
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
- | Generic High Entropy Secret | 09dcd8c | src/mappings/encoding.ts | View secret |
- | Generic High Entropy Secret | 75cdaa7 | src/mappings/encoding.ts | View secret |
- | Generic High Entropy Secret | 75cdaa7 | src/mappings/encoding.ts | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 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!
This is a false positive. @ns212 can I override this, or do you have to do that? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job updating the types properly and making the code cleaner! Only comment I left is regarding the naming, which is only a suggestion that can be ignored :)
1. Ensure your DB is running and up to date (e.g. you recently ran `yarn db:migrate`) | ||
2. Run `yarn gen:code` to regenerate TypeScript types for the GraphQL entities. | ||
3. Run `yarn build` to compile the newly generated code. | ||
4. Run `yarn db:create-migration`, and enter a name for the migration. This will auto-generate it. | ||
5. Run `yarn db:migrate` to apply your new migration. | ||
6. You can now develop the mappings against the new entities. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great update of the readme! 👏
Full indexing tested:
|
1021000
0.12.0
(was0.11.1
)