Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(main): release 1.0.0 #1215

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Apr 14, 2023

🤖 I have created a release beep boop

1.0.0 (2023-04-19)

Features

Bug Fixes

  • apex-language-server: update jar file path (#652) (4a007b4)
  • api/command: instantiate UI before package installation (#810) (6a39b2f)
  • api: refresh registry before installing packages in :MasonInstall (#1128) (9f4e060)
  • async: early return if no suspend functions (#1165) (1840ecc)
  • avoid calling API functions inside fast event (#892) (4d734ae)
  • brighterscript: link correct executable (#931) (9660a81)
  • checkhealth: use non-deprecated versions if possible (#1219) (9048bdb)
  • codelldb: don't symlink executable directly (#374) (1cde8fd)
  • codelldb: require GNU compatible system on linux (#532) (d06095e)
  • crystalline: update linux asset name (#901) (01cba2a)
  • dhall-lsp: github release doesn't always include lsp server asset (#675) (36231e6)
  • dhall: new assets have capitalized naming (#520) (5a25626)
  • doc: duplicate helptag (#1099) (441c9ea)
  • docker-compose-language-service: upstream added a binary (#990) (eb6010a)
  • dotnet: remove unnecessary nil check (#420) (6ed2bf5)
  • drools-lsp: remove unused shell exec wrapper (#925) (db162f3)
  • editorconfig-checker: update Windows assets (#904) (24e78fc)
  • EventEmitter: properly deregister handlers, print errors that occur in handler (#373) (73fb0ea)
  • fantomas: link correct fantomas binany name (#370) (c019223)
  • fetch: set proper iwr header on Windows, reorder tool priority (#531) (3fa66ad)
  • fetch: use correct separator for Windows iwr headers (#1014) (718966f)
  • fix writing pyvenv module wrapper (#1073) (3ee3174)
  • functional: spread function args in _.apply (#770) (2db93f7)
  • gem: don't format executable (#634) (4d68f40)
  • github: fall back to curl/wget if gh is not available (#1181) (e57d9bd)
  • github: use evaluated out_file as asset file value (#1208) (df4bf38)
  • goimports-reviser: use prebuilt github assets (#573) (980f565)
  • health: add scheduler in python3_host_prog check (#1234) (f657fb6)
  • healthcheck completion of mason (#1185) (b54d4e3)
  • health: only check pwsh on Windows (#1232) (5a26b2f)
  • joker: update asset filenames (#685) (27f13da)
  • js-debug-adapter: fix build script (#1088) (50ed860)
  • libuv: shutdown -> close (#816) (10d3917)
  • log: use "log" stdpath (#516) (632f56c)
  • lua-language-server: only install Linux assets on GNU systems (#890) (7344927)
  • mason-registry: don't pass possible nil value to log (#840) (df1dd88)
  • mkdirp if stdpath("state" | "cache") doesn't exist (#1123) (c1f790c)
  • npm: set install-strategy on npm >= 9 (#1179) (c625abf)
  • openscad-lsp: fix bin definition (#876) (a4ebe1f)
  • package: don't call vim API functions inside fast event (#730) (2381f50)
  • package: emit package:uninstall:success registry event (#849) (dac1093)
  • package: emit registry event on abnormal failures (#1061) (35e33e4)
  • package: schedule callback that can only run in main loop (#1172) (1256cec)
  • pip3: expand python3_host_prog path (#519) (e93a299)
  • platform: also accept exit code 1 when checking ldd version (#630) (e14b20c)
  • powershell: close stdin (#1197) (33e0d59)
  • powershell: terminate stdin with newline (#818) (e28907b)
  • powershell: use pwsh if available (#782) (8240d7d)
  • protolint: use Protobuf language (#641) (d3c2156)
  • providers/pypi: fix invalid key name (#610) (bf170f8)
  • provider: use correct name for github (#620) (2627b6e)
  • r-languageserver: pass missing libuv pipe arg (#820) (45e9cbc)
  • r-languageserver: use github releases as version source (#417) (07d949a)
  • registry: use oneshot channel for updating registry (#1168) (2e35781)
  • rome: drop default version pin (#649) (a1f1fb0)
  • rustfmt: use correct asset names and use unzip on windows (#644) (a096949)
  • scripts: setup mason and init registries (#1124) (1fcb620)
  • shfmt, yamlfmt: fix windows detection (#492) (6f70671)
  • solang: llvm13 -> llvm14 (#859) (73831cb)
  • sources: also set .desc property when updating spec (#1095) (63988d8)
  • spawn: always expand cmd if PATH is not modified (#773) (dd04b41)
  • spawn: always expand cmd on Windows (dd04b41)
  • spectral-language-server: build directly from source (#464) (e0268a6)
  • spectral-language-server: link spectral-language-server executable (#666) (30a9451)
  • spectral-language-server: update homepage (#855) (b94f8ff)
  • std: manually call zstd on Windows (#1212) (3664448)
  • taplo: rename files to match upstream (#613) (f01129e)
  • tectonic: pin version (#708) (175408f)
  • terraform-ls: use releases.hashicorp.com (#1002) (511457c)
  • ui: better bottom padding if cmdheight=0 (#902) (5ab101a)
  • ui: do not override existing MasonNormal hl group (#833) (ded89d8)
  • ui: dont early return package updates if no visible packages (#1166) (bd5910e)
  • ui: lower zindex to 45 (#404) (364dd14)
  • ui: remove new lines from error (#1167) (0669f0f)
  • ui: remove new lines from spawn handle string (#1119) (9f6fd51)
  • ui: set severity min & max for namespaced diagnostic config (#738) (66f02fd)
  • vala-lanaguager-server: update meson build commands (#896) (b61d7f1)
  • vala-language-server: use git tag source instead of releases (#856) (38f0d1e)
  • verible: properly format asset file (#657) (8a003fd)
  • visualforce-language-server: remove custom release resolution code (#534) (b0cb03d)
  • visualforce-language-server: update script path (#656) (4f63b13)
  • windows: download registry archive to file instead of piping data (#1189) (84af7a1)
  • yapf: install toml to support parsing .toml config files (#682) (60a03f5)
  • zls: fix Windows x64 target (#948) (3717745)
  • zls: support zst (#622) (b9e8c4a)

This PR was generated with Release Please. See documentation.

@williamboman
Copy link
Owner

@jay-babu 👋 figured I'd ask you since I couldn't find anything in their docs yet. How does one change the CHANGELOG of the release? Do I simply edit the body and then merge?

@jay-babu
Copy link
Contributor

Once the release is made, you can edit the notes. At least that's how I have done it

@github-actions github-actions bot force-pushed the release-please--branches--main--components--mason.nvim branch from 6eba28a to e14ff80 Compare April 15, 2023 10:04
@jay-babu
Copy link
Contributor

@williamboman did that make sense or no?

@williamboman
Copy link
Owner

@williamboman did that make sense or no?

Yeah! I think I'll manually cut the 1.0.0 release and delegate the rest to CI

@github-actions github-actions bot force-pushed the release-please--branches--main--components--mason.nvim branch 9 times, most recently from e6dd2a2 to d4171f1 Compare April 18, 2023 19:06
@github-actions github-actions bot force-pushed the release-please--branches--main--components--mason.nvim branch from d4171f1 to 61e4743 Compare April 19, 2023 10:05
@doctorfree
Copy link

With respect to release creation, the Github CLI tool gh can assist. Each of my projects has a script I call mkrelease which executes gh something like:

gh release create v${VERSION}r${RELEASE} ${DRAFT} \
                  --title "${ANNO}" \
                  --notes-file ReleaseNotes.md \
                  lazyman.sh

where VERSION and RELEASE are something like 1.0.0 and 1, ANNO is the annotation for the tag, and DRAFT is the draft flag (empty or --draft).

Note the --notes-file argument. These are my Release Notes which get included in the Github release. They can reference the CHANGELOG or a CHANGELOG.md could be provided to --notes-file. When creating a release in this manner all that is necessary is to set the version in the VERSION file, edit the Release Notes in ReleaseNotes.md, then invoke mkrelease.

The final argument above, lazyman.sh, is the release artifacts and can be a list of files or regular expression. It globs up all the files you wish to release as artifacts.

Prior to running gh a tag for the release was created with:

git tag -a  "v${VERSION}r${RELEASE}" -m " ${ANNO}"
git push origin "v${VERSION}r${RELEASE}" 

and after gh is run the new tag is fetched.

Perhaps CI can handle your release needs perfectly well. I am just providing this in case you wish to automate release creation from the command line. Here is my full mkrelease script (gittag is another small script I use that just does the git tag ... and git push origin $TAG):

#!/bin/bash

[ -f VERSION ] || {
    echo "VERSION file missing. Exiting."
    exit 1
}
. ./VERSION

usage() {
    printf "\nUsage: mkrelease [-d] [-u]"
    printf "\nWhere:"
    printf "\n\t-d indicates create draft release"
    printf "\n\t-u displays this usage message and exits\n"
    exit 1
}

DRAFT=
while getopts "du" flag; do
    case $flag in
        d)
            DRAFT="--draft"
            ;;
        u)
            usage
            ;;
    esac
done
shift $(( OPTIND - 1 ))

ANNO="Lazyman Version ${VERSION} Release ${RELEASE}"
gittag v${VERSION}r${RELEASE} ${ANNO}

echo "Creating release for version ${VERSION} release ${RELEASE}"

gh release create v${VERSION}r${RELEASE} ${DRAFT} \
                  --title "${ANNO}" \
                  --notes-file ReleaseNotes.md \
                  lazyman.sh

git fetch --tags origin

@williamboman
Copy link
Owner

Thanks @doctorfree! The primary reason I think this particular GitHub action is helpful is because it 1) helps with the procurement of the changelog/release notes based on (conventional) commit history, 2) keeps track of what kind of release to make based on the commit history.

@williamboman
Copy link
Owner

I wonder what happens if I close this. I'll manually cut the initial 1.0.0 release anyways.

@williamboman williamboman deleted the release-please--branches--main--components--mason.nvim branch April 19, 2023 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants