From 677d0a5117e1a36439c2586e9e2d2e73985368f8 Mon Sep 17 00:00:00 2001
From: Rostislav Simonik <rostislav.simonik@technologystudio.sk>
Date: Sat, 22 Jul 2023 07:46:50 +0200
Subject: [PATCH] docs: remove obsolete release doc

fixes #1186
---
 releasing.md | 11 -----------
 1 file changed, 11 deletions(-)
 delete mode 100644 releasing.md

diff --git a/releasing.md b/releasing.md
deleted file mode 100644
index 670ffd03..00000000
--- a/releasing.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Making a release
-
-1. Make sure you have access to publish, by running `$ npm access ls-collaborators`.
-1. While on the main branch, with a clean working directory, `$ git checkout -b release`.
-1. `$ npm run prepare-release`. If that was unsuccessful, investigate. If it was successful, the version is bumped and a new commit exists.
-2. Create a new pull request from this branch. The name of the pull request can be same as the commit message.
-3. Merge the pull request.
-4. Switch to the main branch and `$ git pull`.
-5. `$ git tag v$VERSION`, where `$VERSION` is the new version. For example, `$ git tag v16.0.0`.
-6. `$ git push --tags`
-7. `npm publish`