chore(deps): update dependency kounex/update-day to v0.12.0 - #69
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency kounex/update-day to v0.12.0#69renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/kounex-update-day-0.x
branch
from
July 20, 2026 10:54
67a417a to
84ec97a
Compare
renovate
Bot
force-pushed
the
renovate/kounex-update-day-0.x
branch
from
July 21, 2026 00:50
84ec97a to
2f52278
Compare
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:
0.9.32→0.12.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
kounex/update-day (kounex/update-day)
v0.12.0Compare Source
Full audit of every user-facing command - clarity, correctness, and message quality.
Added
/deletenow asks for confirmation (Delete/Cancel buttons) before actually deleting an Observe, instead of doing it immediately on a single command.Changed
/observe'sscrape-intervalis now optional (it already had a documented "Hourly is the default" - it just wasn't actually possible to omit it before).keep-activedescription on/observeand/edit- it previously read "If you want to deactivate the Observe once it found a change, true by default", which was backwards on both the polarity (truekeeps it active, it doesn't deactivate it) and the stated default (it'sfalse)./scrape(manual trigger) now goes through the same persistence/notification pipeline as the background scheduler, instead of bypassing it entirely - it used to leavelastScrapeAtMS/amountScrapedstale, skip auto-deactivation on a found change, and could cause the same change to be DM'd to the user twice (once never, once later from the scheduler catching up).GuildMessageReactions,GuildVoiceStates) left over from the bot this project was originally forked from.true/false./delete,/edit,/list,/reactivate, and/scrapeinto one shared helper.Fixed
/admin list-observes'sthis-guild/active-onlyoptions were documented as "true by default" but actually defaulted to showing every guild's Observes, including inactive ones, when left unset - and explicitly passingthis-guild: falsedid the opposite of what it should. An admin running this with no arguments, expecting just their own guild's active Observes as documented, would see every other guild's data on this bot too./reactivatedidn't resetconsecutiveTimeouts, so an Observe deactivated for hitting the timeout limit would immediately re-deactivate after just one more timeout instead of getting a fresh run of the full limit.buildObserveOverview(used by/admin list-observes) fetched each user's Discord profile one at a time in a loop instead of in parallel./list,/admin list-observes) had no guard against Discord's 1024-character field-value limit - a guild/user with enough Observes would have hit an API error building the embed. Now truncates safely with a "…and N more" note, keeping all columns aligned to the same row count.v0.11.2Compare Source
Changed
/editno longer requires re-entering every field. Onlycurrent-name(which Observe to edit) is required -name,url,text,scrape-interval,css-selectorandkeep-activeare all optional now, and any left empty keep their current value instead of being overwritten or reset to a default. This also fixes a latent bug where editing any field silently resetkeep-activeback tofalseif you didn't re-specify it.css-selectorcan be explicitly cleared back to whole-page search by typingnone.v0.11.1Compare Source
Fixed
puppeteer.launch()had no--no-sandboxflag, so Chrome crashed immediately in this container (missing sandbox privileges) - every single scrape was silently hitting this and surfacing as a generic timeout. This was breaking every Observe, on every site.HeadlessChrome) block requests from an obviously-automated browser - now presented as regular desktop Chrome (same bundled build, just without the giveaway tag).content-visibility: auto(a real, increasingly common perf optimization) render as empty text until scrolled into view - the target element/scope is now scrolled into view before reading its text, same as a real visitor would encounter it.v0.11.0Compare Source
Changed
/observeand/editno longer require a CSS selector. By default the bot now searches the whole page's visible text for the phrase you give it;css-selectoris now optional and only needed to narrow the search if that phrase could also show up elsewhere on the page (nav, other products, etc). This removes the main pain point of finding a precise, unique selector for text buried in a deeply nested/generic tag.current-textoption totextand the underlyingcurrentTextcolumn towatchTextto match its actual meaning: the phrase you're watching for, which you'll be notified about once it's no longer found on the page.dom-element-propertyoption entirely — it only made sense when pointing at one exact element, which conflicts with the new default of searching a broader area, and nothing was using it.v0.10.0Compare Source
Added
Changed
node:22-slim(Node 18 is EOL) and updateddiscord.js,puppeteer,inversify,prisma,execa,typescript, and related dependencies to current versions.tiniis now actually wired up as the container's PID 1 (ENTRYPOINT) for proper signal handling/zombie reaping — it was previously installed but unused.YOUTUBE_API_KEY,SPOTIFY_CLIENT_ID/SECRET, and other leftovers from the bot template this project was originally forked from).Fixed
Array.prototype.splicecalled without a delete count), causing duplicate/concurrent scrapes.guildCreatehandler that could crash the entire bot process (e.g. a user with DMs disabled).browser.close()call.breakin the/scrapecommand's result handling that caused a detected change to display as "No change".Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, 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.