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

fix(deps): update tauri monorepo to 1.0.0 #14

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 14, 2022

Mend Renovate

This PR contains the following updates:

Package Type Update Change
tauri (source) dependencies patch 1.0.0-rc.14 -> 1.0.0
tauri-build (source) build-dependencies patch 1.0.0-rc.12 -> 1.0.0

Release Notes

tauri-apps/tauri

v1.0.0

Compare Source

Updating crates.io index

Cargo Audit

Fetching advisory database from `https://github.com/RustSec/advisory-db.git`
      Loaded 417 security advisories (from /home/runner/.cargo/advisory-db)
    Updating crates.io index
    Scanning Cargo.lock for vulnerabilities (448 crate dependencies)

[1.0.0]

  • Allow choosing multiple folders in dialog.open.
  • Upgrade to stable!

Cargo Publish

Updating crates.io index
   Packaging tauri v1.0.0 (/home/runner/work/tauri/tauri/core/tauri)
   Uploading tauri v1.0.0 (/home/runner/work/tauri/tauri/core/tauri)

v1.0.0-rc.17

Compare Source

Updating crates.io index

Cargo Audit

Fetching advisory database from `https://github.com/RustSec/advisory-db.git`
      Loaded 417 security advisories (from /home/runner/.cargo/advisory-db)
    Updating crates.io index
    Scanning Cargo.lock for vulnerabilities (445 crate dependencies)

[1.0.0-rc.17]

  • Add Menu::os_default which will create a menu filled with default menu items and submenus.

Cargo Publish

Updating crates.io index
   Packaging tauri v1.0.0-rc.17 (/home/runner/work/tauri/tauri/core/tauri)
   Uploading tauri v1.0.0-rc.17 (/home/runner/work/tauri/tauri/core/tauri)

v1.0.0-rc.16

Compare Source

v1.0.0-rc.15

Compare Source

Updating crates.io index

Cargo Audit

Fetching advisory database from `https://github.com/RustSec/advisory-db.git`
      Loaded 417 security advisories (from /home/runner/.cargo/advisory-db)
    Updating crates.io index
    Scanning Cargo.lock for vulnerabilities (445 crate dependencies)

[1.0.0-rc.15]

  • Read the tray icon path relatively to the config directory.
    • Bumped due to a bump in tauri-codegen.
    • 562e8ca2 fix(codegen): tray icon path is relative to the config directory on 2022-06-15

Cargo Publish

Updating crates.io index
   Packaging tauri-build v1.0.0-rc.15 (/home/runner/work/tauri/tauri/core/tauri-build)
   Uploading tauri-build v1.0.0-rc.15 (/home/runner/work/tauri/tauri/core/tauri-build)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@netlify
Copy link

netlify bot commented Jun 14, 2022

Deploy Preview for redwoodblog-dev ready!

Name Link
🔨 Latest commit 7ce4daa
🔍 Latest deploy log https://app.netlify.com/sites/redwoodblog-dev/deploys/62acf094b17c1d0008d87362
😎 Deploy Preview https://deploy-preview-14--redwoodblog-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@renovate renovate bot force-pushed the renovate/tauri-monorepo branch 5 times, most recently from fc69372 to 35fe4d6 Compare June 16, 2022 03:30
@renovate renovate bot changed the title chore(deps): update tauri monorepo fix(deps): update tauri monorepo Jun 16, 2022
@renovate renovate bot force-pushed the renovate/tauri-monorepo branch from 35fe4d6 to 2d667d2 Compare June 16, 2022 05:47
@renovate renovate bot changed the title fix(deps): update tauri monorepo fix(deps): update tauri monorepo to v1.0.0 Jun 16, 2022
@renovate renovate bot changed the title fix(deps): update tauri monorepo to v1.0.0 fix(deps): update tauri monorepo Jun 16, 2022
@renovate renovate bot force-pushed the renovate/tauri-monorepo branch 2 times, most recently from 5de72da to 5bac138 Compare June 17, 2022 01:14
@renovate renovate bot force-pushed the renovate/tauri-monorepo branch from 5bac138 to 7ce4daa Compare June 17, 2022 21:22
@renovate renovate bot changed the title fix(deps): update tauri monorepo fix(deps): update tauri monorepo to 1.0.0 Jun 17, 2022
@pull-request-quantifier-deprecated

This PR has 135 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       : +102 -33
Percentile : 47%

Total files changed: 2

Change summary by file extension:
.lock : +100 -31
.toml : +2 -2

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 detetcted.
  • 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.

@sonarcloud
Copy link

sonarcloud bot commented Jun 26, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants