<commit_before>/**
 * @fileoverview Creates new issues after specified old issues are closed
 * @author <NAME>
 */

"use strict";

const moment = require("moment-timezone");

/**
 * Gets the desired issue body for a release issue, given the date of the release.
 * @param {Moment} releaseDate The date of the release, as Moment UTC date
 * @returns {Promise<string>} The text of the issue
 */
async function getReleaseIssueBody(releaseDate) {
    return `

The next scheduled release will occur on ${releaseDate.format("dddd, MMMM Do, YYYY")}.

## Release Day Checklist

- [ ] Remove the 'tsc agenda' label on this issue
- [ ] Review open pull requests and merge any that are [ready](https://eslint.org/docs/maintainer-guide/pullrequests#when-to-merge-a-pull-request)
- [ ] Start the release on [Jenkins](https://jenkins.eslint.org)
- [ ] Update the release blog post with a "Highlights" section
- [ ] Make a release announcement on Twitter
- [ ] Make a release announcement in the Discord '#announcements' channel
- [ ] Add a comment to this issue saying the release is out
- [ ] Add the 'patch release pending' label to this issue

## Two Days After Release Day Checklist

Typically Monday for regular releases; two days after patch releases.

- [ ] Check the issues list for any regression issues

## No Regressions Checklist

- [ ] Remove the 'patch release pending' label from this issue
- [ ] Close this issue

## Patch Release Checklist

- [ ] Resolve the regression by merging any necessary fixes
- [ ] Start the release on [Jenkings](https://jenkins.eslint.org)
- [ ] Update the release blog post with a "Highlights" section
- [ ] Make a release announcement on Twitter
- [ ] Make a release announcement in the Discord '#announcements' channel
- [ ] Add a comment to this issue saying the release is out
- [ ] Wait two days and repeat the Two Days After a Release checklist<commit_msg>Fix: typo jenkings (#138)<commit_after>/**
 * @fileoverview Creates new issues after specified old issues are closed
 * @author <NAME>
 */

"use strict";

const moment = require("moment-timezone");

/**
 * Gets the desired issue body for a release issue, given the date of the release.
 * @param {Moment} releaseDate The date of the release, as Moment UTC date
 * @returns {Promise<string>} The text of the issue
 */
async function getReleaseIssueBody(releaseDate) {
    return `

The next scheduled release will occur on ${releaseDate.format("dddd, MMMM Do, YYYY")}.

## Release Day Checklist

- [ ] Remove the 'tsc agenda' label on this issue
- [ ] Review open pull requests and merge any that are [ready](https://eslint.org/docs/maintainer-guide/pullrequests#when-to-merge-a-pull-request)
- [ ] Start the release on [Jenkins](https://jenkins.eslint.org)
- [ ] Update the release blog post with a "Highlights" section
- [ ] Make a release announcement on Twitter
- [ ] Make a release announcement in the Discord '#announcements' channel
- [ ] Add a comment to this issue saying the release is out
- [ ] Add the 'patch release pending' label to this issue

## Two Days After Release Day Checklist

Typically Monday for regular releases; two days after patch releases.

- [ ] Check the issues list for any regression issues

## No Regressions Checklist

- [ ] Remove the 'patch release pending' label from this issue
- [ ] Close this issue

## Patch Release Checklist

- [ ] Resolve the regression by merging any necessary fixes
- [ ] Start the release on [Jenkins](https://jenkins.eslint.org)
- [ ] Update the release blog post with a "Highlights" section
- [ ] Make a release announcement on Twitter
- [ ] Make a release announcement in the Discord '#announcements' channel
- [ ] Add a comment to this issue saying the release is out
- [ ] Wait two days and repeat the Two Days After a Release checklist
{'fraction_non_alphanumeric': 0.09265596209528823, 'fraction_numerical': 0.0007896814951302974, 'mean_word_length': 4.0, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4610530', 'n_tokens_mistral': 1051, 'n_tokens_neox': 1018, 'n_words': 480}