From 75d12e6e95d547aff96d2e1676c217e393df8d7f Mon Sep 17 00:00:00 2001 From: Luke Heath Date: Fri, 4 Mar 2022 12:29:12 -0600 Subject: [PATCH] Update broken relative url links to absolute urls (#4464) --- docs/Contributing/Releasing-Fleet.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/Contributing/Releasing-Fleet.md b/docs/Contributing/Releasing-Fleet.md index 5cf03ac47a..8059466516 100644 --- a/docs/Contributing/Releasing-Fleet.md +++ b/docs/Contributing/Releasing-Fleet.md @@ -2,7 +2,7 @@ Note: Please prefix versions with `fleet-v` (eg. `fleet-v4.0.0`) in git tags, Helm charts, and NPM configs. -1. Update the [CHANGELOG](../../CHANGELOG.md) with the changes that have been made since the last +1. Update the [CHANGELOG](https://github.com/fleetdm/fleet/blob/main/CHANGELOG.md) with the changes that have been made since the last Fleet release. Use `make changelog` to pull the changes files into `CHANGELOG.md`, then manually edit. When editing, order the most relevant/important changes at the time, and try to make the tone and syntax of the written language match throughout. `make changelog` will stage all changes @@ -14,9 +14,9 @@ Note: Please prefix versions with `fleet-v` (eg. `fleet-v4.0.0`) in git tags, He Update version numbers in the relevant files: - - [package.json](../../tools/fleetctl-npm/package.json) (do not yet `npm publish`) - - [Helm chart](../../charts/fleet/Chart.yaml) and [values file](../../charts/fleet/values.yaml) - - [Terraform variables](../../tools/terraform/variables.tf) + - [package.json](https://github.com/fleetdm/fleet/blob/main/tools/fleetctl-npm/package.json) (do not yet `npm publish`) + - [Helm chart](https://github.com/fleetdm/fleet/blob/main/charts/fleet/Chart.yaml) and [values file](https://github.com/fleetdm/fleet/blob/main/charts/fleet/values.yaml) + - [Terraform variables](https://github.com/fleetdm/fleet/blob/main/tools/terraform/variables.tf) Commit these changes via Pull Request and pull the changes on the `main` branch locally. Check that `HEAD` of the `main` branch points to the commit with these changes. @@ -69,7 +69,7 @@ Note: Please prefix versions with `fleet-v` (eg. `fleet-v4.0.0`) in git tags, He When editing is complete, publish the release. 4. Publish the new version of `fleetctl` on NPM. Run `npm publish` in the - [fleetctl-npm](../../tools/fleetctl-npm/) directory. Note that NPM does not allow replacing a + [fleetctl-npm](https://github.com/fleetdm/fleet/tree/main/tools/fleetctl-npm) directory. Note that NPM does not allow replacing a package without creating a new version number. Take care to get things correct before running `npm publish`! @@ -128,7 +128,7 @@ must be created and relevant changes cherry-picked onto that branch: be invoked to push a container image for QA with `fleetctl preview` (eg. `fleetctl preview --tag patch-fleet-v4.3.1`). 4. Check in the GitHub UI that Actions ran successfully for this branch and perform [QA smoke - testing](../../.github/ISSUE_TEMPLATE/smoke-tests.md). + testing](https://github.com/fleetdm/fleet/blob/main/.github/ISSUE_TEMPLATE/smoke-tests.md). 5. Follow the standard release instructions at the top of this document. Be sure that modifications to the changelog and config files are commited _on the `patch-*` branch_. When the patch has been