ci(NODE-6036): upgrade gha and add dependabot #33
Conversation
| ### Description | ||
|
|
||
| #### What is changing? | ||
|
|
||
| ##### Is there new documentation needed for these changes? | ||
|
|
||
| #### What is the motivation for this change? | ||
|
|
||
| <!-- If this is a bug, it helps to describe the current behavior and a clear outline of the expected behavior --> | ||
| <!-- If this is a feature, it helps to describe the new use case enabled by this change --> | ||
|
|
||
| <!-- | ||
| Contributors! | ||
| First of all, thank you so much!! | ||
| If you haven't already, it would greatly help the team review this work in a timely manner if you create a JIRA ticket to track this PR. | ||
| You can do that here: https://jira.mongodb.org/projects/NODE | ||
| --> | ||
|
|
||
| ### Release Highlight | ||
|
|
||
| <!-- RELEASE_HIGHLIGHT_START --> | ||
|
|
||
| ### Fill in title or leave empty for no highlight | ||
|
|
There was a problem hiding this comment.
How come we are adding in an entire new template? I was under the impression we already had one.
There was a problem hiding this comment.
Nevermind, I'm realizing this is just adding the release highlight template to another repo of ours. (I'll wait on your confirmation before I approve.)
There was a problem hiding this comment.
Another question I have is where our automation for PRs + releases is?
There was a problem hiding this comment.
We don't have release automation set up on this repo, I figure it is likely we will want to, maybe when we centralize the scripting that makes that all possible. No harm in having a place to put highlights that can be manually rolled up into a release. I doubt a release on this package will have more than a few changes at a time.
Description
What is changing?
Is there new documentation needed for these changes?
No
What is the motivation for this change?
Double check the following
npm run lintscripttype(NODE-xxxx)[!]: descriptionfeat(NODE-1234)!: rewriting everything in coffeescript