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

Use Node 20, Update Yarn and some dependencies. #3468

Merged
merged 23 commits into from
Oct 31, 2023
Merged

Conversation

Akamig
Copy link
Member

@Akamig Akamig commented Oct 30, 2023

  • Formatter Rome has been discontinued. rollback to prettier.
  • Bump Yarn to v4 (4.0.1)
  • Bump typescript to ^4.5.0 (4.9.5)
    • nanobundle supports v5 ts though, it's dependancies does not supports v5 yet
  • Add WebCrypto export adapter for it's environment (CJS,MJS,Browser)
  • Add 'IsDigest" in tx sign.ts

Update

  • Let AwsKmsAccount handle digest / non digested form of Sign Command
  • Add WebCrypto export adapter for aws-kms-account

@Akamig Akamig added ci & cd Related to CI & CD on Azure Pipelines & GitHub Actions dependencies Pull requests that update a dependency file labels Oct 30, 2023
@Akamig Akamig requested review from XxshiftxX and moreal October 30, 2023 06:13
@Akamig Akamig self-assigned this Oct 30, 2023
@CLAassistant
Copy link

CLAassistant commented Oct 30, 2023

CLA assistant check
All committers have signed the CLA.

@moreal moreal requested a review from tkiapril October 30, 2023 06:29
XxshiftxX
XxshiftxX previously approved these changes Oct 30, 2023
@Akamig Akamig force-pushed the update-ts-packages branch 3 times, most recently from 83309ad to 3426d62 Compare October 30, 2023 06:41
@Akamig
Copy link
Member Author

Akamig commented Oct 30, 2023

........It should work now. I guess. maybe.

@planetarium/tx/package.json Outdated Show resolved Hide resolved
.github/workflows/yarn.yaml Outdated Show resolved Hide resolved
@@ -7,7 +7,7 @@ import Signature from "./Signature.js";
export interface Account {
getAddress(): Promise<Address>;
getPublicKey(): Promise<PublicKey>;
sign(message: Message): Promise<Signature>;
sign(message: Message, isDigest?: boolean): Promise<Signature>;
Copy link
Contributor

@moreal moreal Oct 30, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't okay to update Account too? I'm not sure it can be added to the interface level.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's optional flag, so probably....

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After some discussions, we decided to just handle this inside AWS-KMS

@moreal moreal marked this pull request as draft October 30, 2023 06:46
@moreal
Copy link
Contributor

moreal commented Oct 30, 2023

Please press button read-for-review when the CI passed 🙏🏻

@tkiapril tkiapril changed the title Use Node 20, Update Yarn and some dependancies. Use Node 20, Update Yarn and some dependencies. Oct 30, 2023
@Akamig Akamig force-pushed the update-ts-packages branch from fab5fde to 7965998 Compare October 30, 2023 06:51
tkiapril
tkiapril previously approved these changes Oct 30, 2023
tkiapril
tkiapril previously approved these changes Oct 30, 2023
@Akamig Akamig force-pushed the update-ts-packages branch from 10957ae to a3e4579 Compare October 30, 2023 07:28
@Akamig
Copy link
Member Author

Akamig commented Oct 30, 2023

F7ULFrQWEAACj2Q

@Akamig Akamig force-pushed the update-ts-packages branch from fd5b100 to 4df9f60 Compare October 30, 2023 07:47
@Akamig Akamig force-pushed the update-ts-packages branch from 4df9f60 to 75dd1ed Compare October 30, 2023 07:54
@Akamig Akamig force-pushed the update-ts-packages branch from e216152 to e0d5c13 Compare October 30, 2023 08:17
@Akamig Akamig marked this pull request as ready for review October 30, 2023 08:24
@Akamig Akamig requested a review from tkiapril October 30, 2023 08:25
@Akamig
Copy link
Member Author

Akamig commented Oct 30, 2023

yarn / build (lts/*) (pull_request) has failed due to AWS API timeout,
Check yarn / build (lts/*) (push) instead.
(It barely succeed in time , maybe longer timeout for this test is advised.)

tkiapril
tkiapril previously approved these changes Oct 30, 2023
tkiapril
tkiapril previously approved these changes Oct 30, 2023
@Akamig Akamig force-pushed the update-ts-packages branch from 7545f05 to 2271404 Compare October 30, 2023 09:57
@pull-request-quantifier-deprecated

This PR has 132 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Medium
Size       : +70 -62
Percentile : 46.4%

Total files changed: 25

Change summary by file extension:
.yaml : +2 -2
.json : +40 -22
.cjs : +0 -26
.js : +3 -1
.yml : +3 -6
.ts : +22 -5

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@@ -1,15 +1,17 @@
{
"include": ["./src", "*.d.ts", "*.ts"],
"include": ["./src", "*.d.ts", "src/*.ts"],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't it included by ./src? 👀

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just src also works since it's "at" rootDir.

@moreal
Copy link
Contributor

moreal commented Oct 30, 2023

I've run CI in dry-run mode. If the job passes, this pull request can be merged. https://github.com/planetarium/libplanet/actions/runs/6692173135/job/18180817778 Passed! ✅

@codecov
Copy link

codecov bot commented Oct 31, 2023

Codecov Report

Merging #3468 (51757a5) into main (0e4d8e5) will increase coverage by 0.02%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3468      +/-   ##
==========================================
+ Coverage   79.11%   79.14%   +0.02%     
==========================================
  Files         343      343              
  Lines       11834    11834              
==========================================
+ Hits         9363     9366       +3     
+ Misses       2471     2468       -3     

see 2 files with indirect coverage changes

@Akamig Akamig merged commit 8b235a9 into main Oct 31, 2023
23 of 24 checks passed
greymistcube pushed a commit to greymistcube/libplanet that referenced this pull request Nov 20, 2023
* use ES2022

* add isDigest

* WebCrypto Export

* yarn upgrade (4.0.1)

* Fix typo

* Use Typescript ^4.5.0 (due to nanobundle dependancy)

* Update Nanobundle 1.6.0

* Use NodeNext (implies EsNext)

* Add

* use 20 in CI

* use lts/*

* WebCrypto Shim

* Webcrypto Shim 2.0 Electric Boogaloo

* Update .github/workflows/yarn.yaml

Co-authored-by: Lee Dogeon <[email protected]>

* Add rootdir

* isDigest Removal

* Add engines

* Rome ignore.

* add

* Remove Digest Completely

* Add Bencodex

* Test

* Remove bencodex

---------

Co-authored-by: Lee Dogeon <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci & cd Related to CI & CD on Azure Pipelines & GitHub Actions dependencies Pull requests that update a dependency file Medium
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants