possible to check for milestone starts with v condition before changing?

https://s.tape.sh/mPacl92l

• look into use of Promise.all and Promise.allSettled
• #71
• #70
• #66
• fix logger cluttering github.test.ts
• improve use of TS
• improve visual output of validate (specifically, add loading spinner); and it seems like exec doesn't wait on async functions
• [Bug?]: it seems like you can't expect functions to throw in jest a62bb07
• clean up scripts
• fix Jun 26 02:47:07 PM 05:47:07 🚨 Function "" was not found. in render deploy logs
• documentation
• reconsider process.env.OWNER and process.env.REPO
• how does it handle other repos?
• consider using a queue for validate https://ryanchenkie.com/blog/how-to-use-queues-with-redwoodjs
• #64
• reconsider convention around error naming
• maybe validations shouldn't be linear?
• add noire munich
• update graphql to ProjectV2 https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/#%F0%9F%A4%96-graphql-api-improvements
• previous cycle error needs to handle draft issues; the logs were truncated (on render)
• logging in handleContentLabeled now showing up way later (but I suppose that's to be expected)
• more could be and needs to be done for triage—maybe a custom UI?

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update octokit monorepo (@octokit/webhooks-types, octokit)
• chore(deps): update octokit monorepo (major) (@octokit/webhooks-types, octokit)
• fix(deps): update dependency msw to v1
• fix(deps): update react monorepo to v18 (major) (react, react-dom)
• fix(deps): update redwood monorepo to v5 (major) (@redwoodjs/api, @redwoodjs/api-server, @redwoodjs/core, @redwoodjs/forms, @redwoodjs/graphql-server, @redwoodjs/router, @redwoodjs/web)
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency clipanion to v3.2.1
• chore(deps): update dependency node-fetch to v2.6.12
• chore(deps): update dependency date-fns to v2.30.0
• chore(deps): update yarn to v3.6.1
• fix(deps): update dependency @snaplet/copycat to v0.15.1
• fix(deps): update dependency msw to v0.49.3
• fix(deps): update redwood monorepo to v3.8.0 (@redwoodjs/api, @redwoodjs/api-server, @redwoodjs/core, @redwoodjs/forms, @redwoodjs/graphql-server, @redwoodjs/router, @redwoodjs/web)
• chore(deps): update dependency chalk to v5
• chore(deps): update dependency node-fetch to v3
• chore(deps): update node.js to v18
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

If there's no iterations in the Cycle field, yarn validate throws with:

Error in script: Cannot read properties of undefined (reading 'id')

It's not strictly necessary but I'm not sure why this doesn't seem to work.

Bot didn't work on this PR:
redwoodjs/redwood#2795

Doing it now manually.

While we're using the bot to see what hiccups it has / what features we want, here are some immediate next steps:

• integrate with slack for monitoring
• write tests!
• -> PR linked to issue -> issue comes off board
• use RedwoodJS's api side
• type more things, probably via comments (autocomplete is a godsend here)
• try converting more stuff to graphql to see if it makes a difference
  • in particular, every github resource has a globally unique node_id. it feels like we should be able to cache milestones node_ids somehow so we don't have to go fetch it everytime