chore(deps): update dependency deno to v2.8.0#184
Merged
Conversation
decafRunning deployments in test mode. Results will appear below. ...🟩 squash 🟩 merge method... 🌴 It will not trigger a deployment. No new version will be deployed. Learn moreLatest release: 0.15.0 Commit of latest release: 8478d77 Commits since last release: - chore(deps): update dependency deno to v2.8.0 This PR contains the following updates:
Release Notesdenoland/deno (deno)
|
| Update | Change |
|---|---|
| lockFileMaintenance | All locks refreshed |
🔧 This Pull Request updates lock files to use the latest dependency
versions.
Configuration
📅 Schedule: (in timezone America/Chicago)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get
config
help if
that's undesired.
- If you want to rebase/retry this PR, check
this box
This PR was generated by Mend Renovate.
View the repository job
log.
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
- ci: disable deno frozen lock-file to make CI/renovatebot setup less complex (#181)
Problem
having frozen lock file has been really annoying, but especially because
of renovatebot.
even with frozen disabled, from my understanding, deno still uses lock
files. I dont have a lot of experience with the default deno behavior
where frozen is off but lock files are on. I want to try it out.
there is a new feature being added to renovatebot that allows you to
tell renovatebot to run '--frozen false' but I am not sure when it will
be launched. when it does, we could enable frozen in the deno.jsonc
again and still not need the github action for updating lock file.
Solution
disable frozen lock files from deno config so we use the default
behavior.
Testing
- Added automated tests.
- Manually tested. If you check this box, provide instructions for
others to test, too.
After merging this PR, I am going to run renovatebot to see if it
successfully updates some deno dependencies and also the lock file.
Notes for reviewers
- build: simplify AGENTS.md and reduce token usage running tests (#180)
Related GitHub Issues
Problem
AGENTS.md uses too many tokens.
- when you run tests, it adds the entire stdout to context.
- I tend to use very small and simple files with less stuff in it.
let's try deleting a ton of the content.
Solution
- tell agent to use junit report for finding failures to fix
- remove everything except commands to run.
Testing
- Added automated tests.
- Manually tested. If you check this box, provide instructions for
others to test, too.
Notes for reviewers
...🟩 rebase 🟩 merge method... 🌴 It will not trigger a deployment. No new version will be deployed.
Learn more
Latest release: 0.15.0
Commit of latest release: 8478d77
Commits since last release:
- chore(deps): update dependency deno to v2.8.0
- ci: delete lockfile update workflow (#183)
follow-up to: #181 where we
just delete the file that was commented out. it's not needed anymore
after testing success without it.
- chore(deps): lock file maintenance (#182)
This PR contains the following updates:
| Update | Change |
|---|---|
| lockFileMaintenance | All locks refreshed |
🔧 This Pull Request updates lock files to use the latest dependency
versions.
Configuration
📅 Schedule: (in timezone America/Chicago)
- Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (
* 0-3 * * 1)
- Between 12:00 AM and 03:59 AM, only on Monday (
- Automerge
- At any time (no schedule defined)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get
config
help if
that's undesired.
- If you want to rebase/retry this PR, check
this box
This PR was generated by Mend Renovate.
View the repository job
log.
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
- ci: disable deno frozen lock-file to make CI/renovatebot setup less complex (#181)
Problem
having frozen lock file has been really annoying, but especially because
of renovatebot.
even with frozen disabled, from my understanding, deno still uses lock
files. I dont have a lot of experience with the default deno behavior
where frozen is off but lock files are on. I want to try it out.
there is a new feature being added to renovatebot that allows you to
tell renovatebot to run '--frozen false' but I am not sure when it will
be launched. when it does, we could enable frozen in the deno.jsonc
again and still not need the github action for updating lock file.
Solution
disable frozen lock files from deno config so we use the default
behavior.
Testing
- Added automated tests.
- Manually tested. If you check this box, provide instructions for
others to test, too.
After merging this PR, I am going to run renovatebot to see if it
successfully updates some deno dependencies and also the lock file.
Notes for reviewers
- build: simplify AGENTS.md and reduce token usage running tests (#180)
Related GitHub Issues
Problem
AGENTS.md uses too many tokens.
- when you run tests, it adds the entire stdout to context.
- I tend to use very small and simple files with less stuff in it.
let's try deleting a ton of the content.
Solution
- tell agent to use junit report for finding failures to fix
- remove everything except commands to run.
Testing
- Added automated tests.
- Manually tested. If you check this box, provide instructions for
others to test, too.
Notes for reviewers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.7.14→2.8.0Release Notes
denoland/deno (deno)
v2.8.0Compare Source
Read more: http://deno.com/blog/v2.8
deno audit fixas alias fordeno audit --fix(#34273)deno bump-versionsubcommand (#30562)deno whysubcommand (#32908)deno bump-version(#33689)Deno.core.loadExtScript()for lazy-loaded scripts (#33739)(#32432)
(#34201)
(#34203)
support (#33603)
(#32785)
deno install -gunprefixed packages(#34290)
catalog:protocol for centralized dependency versions inworkspaces (#32947)
(#33805)
(#32855)
deno cisubcommand (#34235)deno packcommand to create npm tarballs (#32139)deno transpilesubcommand (#32691)(#33247)
deno audit --fix(#32909)(#33883)
(#33730)
evaluation (#33278)
module (#34058)
(#33944)
(#33928)
runtime (#33667)
createImageBitmapcorrectly (#34285)(#34023)
wrong error (#34011)
(#33750)
codes (#33921)
limitsproperty onnode:sqliteDatabaseSync (#33106)support modifyPrototype option in util.deprecate (#33660)
salt with Node (#33757)
(ws://host:port/UUID) (#33592)
destroynamed export (#33573)(#33715)
(#33964)
(#34262)
(#34195)
(#33716)
dual-stack (#33617)
(#33941)
and ignore passphrase (#33770)
(#33769)
(#33577)
--pending-deprecation (#33594)
(#33819)
instead of throwing (#33679)
without END_STREAM (#33644)
(#33740)
and module.parent (#34086)
HttpRequest (#33826)
(#33618)
extensions in config (#33824)
(#33812)
keys (#33811)
createSecureContext (#33686)
internalBinding (#33732)
internalBinding (#33742)
internalBinding (#33729)
getServername op (#33725)
EandSystemErrorfrominternal/errors(#34080)constants (#33726)
name (#33666)
pushPromise (#33741)
(#34088)
(#33665)
top-level throws (#34048)
EC curve names (#33782)
session error event (#33630)
request timeout (#33836)
runner (#33749)
(#33813)
PerformanceObserver entries (#33796)
node:test (#33755)
to accepted (#33828)
(#33762)
internal/validators (#33673)
number" (#33711)
builtin redirects (#34219)
diffieHellman (#33761)
(#33831)
(#33677)
module.register() (#33920)
await test(...)deadlock in node:test(#33947)
and res (#33825)
(#34258)
calls (#33832)
--experimental-loader flag (#33906)
destroy code (#33637)
diffieHellman (#33772)
resumption (#33693)
tests (#33708)
(#33758)
encodingoption infs.watch(#33634)signaloption infs.watch/fs.promises.watch(#33650)
(#33756)
processes on unix (#33605)
(#33731)
retry (#34060)
calls (#33774)
(#34234)
http.ServerResp (#33820)
clientCertEngine is set (#33691)
(#33808)
(#34183)
respondWithFile (#33792)
(#33645)
(#33798)
(#33745)
false-positive (#33714)
nghttp2_option_set_max_settings (#33790)
missing args (#34017)
(#33652)
(#33651)
(#33971)
(#34010)
(#33721)
catalog:protocol in overrides (#33799)collected' (#33735)
deno update --lockfile-onlyshould not update config (#33746)--watch-excludefilter to file change events (#33854)(#33896)
[eval]URL for inspector (#34192)scripts (#33778)
(#33779)
(#33818)
(#33817)
scripts (#33801)
Request/fetch/Response.json (#33999)
fixed length of sequence (#33688)
(#33925)
lazy-loaded JS (#33967)
lazy-loaded JS (#33951)
lazy-loaded scripts (#33830)
ESM (#33936)
lazy-loaded ESM (#33939)
(#33932)
(#33881)
lazy-loaded JS (#33960)
(#33821)
nextTick (#33862)
(#33961)
(#33692)
(#33860)
Configuration
📅 Schedule: (in timezone America/Chicago)
* * * * 0,6)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.