From 079576415af7e25116f1cec0a508a3a43344416b Mon Sep 17 00:00:00 2001 From: Phidica Veia Date: Tue, 16 Apr 2019 21:09:00 +0930 Subject: [PATCH] Prepare for new release --- CHANGELOG.md | 6 +++--- CONTRIBUTING.md | 2 +- messages.json | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index beb78db..de19fc5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,8 +1,8 @@ Changelog ========= -2.4.0-rc1 ---------- +2.4.0 +----- Improvements: - Support the `[ ]` form of `test` (#8) @@ -25,7 +25,7 @@ Improvements: - `keyword.operator.redirect` - `keyword.operator.range` -Bugfix: +Bugfixes: - Some structures were not highlighted correctly if they were immediately followed by the EOF - Unescaped spaces in brace expansion weren't marked up as invalid - Quoted integers were not allowed as file descriptors in redirection diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ab2a154..0f5c9aa 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -26,7 +26,7 @@ Ensure `CHANGELOG.md` has a new version number, and all *relevant* committed cha - Only pluralise headings for lists of more than one item. - Be aware that the text is copied directly to the GitHub release description, so stick to valid markdown. -Bump the version number in `messages.json` to the new version number in `CHANGELOG.md`. +Bump the version number corresponding to `Messages/changes.md` in `messages.json` to the new version number in `CHANGELOG.md`. If there's a major addition, add a news message and link it in `messages.json`. diff --git a/messages.json b/messages.json index 10f9bd6..dc42985 100644 --- a/messages.json +++ b/messages.json @@ -1,5 +1,5 @@ { - "2.3.0": "Messages/changes.md", + "2.4.0": "Messages/changes.md", "2.3.0": "Messages/news-2.3.0.md", "2.0.0": "Messages/news-2.0.0.md" }