From 9ea94cb6ccefcace3c28faeb24f97b0a9eacb697 Mon Sep 17 00:00:00 2001 From: ddavison Date: Fri, 23 May 2014 15:16:51 -0400 Subject: [PATCH] =?UTF-8?q?=E2=93=90=E2=93=93=E2=93=93=E2=93=98=E2=93=9D?= =?UTF-8?q?=E2=93=96=20=E2=93=9F=E2=93=90=E2=93=A3=E2=93=92=E2=93=97=20?= =?UTF-8?q?=E2=93=A3=E2=93=9E=20=E2=93=93=E2=93=9E=E2=93=92=E2=93=A2?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/publishing-a-package.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/publishing-a-package.md b/docs/publishing-a-package.md index a5a45b25c..fd5eaf952 100644 --- a/docs/publishing-a-package.md +++ b/docs/publishing-a-package.md @@ -75,13 +75,18 @@ credentials are stored securely in your [keychain][keychain] once you login. :tada: Your package is now published and available on atom.io. Head on over to `http://atom.io/packages/my-package` to see your package's page. +The `major` option to the publish command tells apm to increment the first +digit of the version before publishing so the published version will be `1.0.0` +and the Git tag created will be `v1.0.0`. Though since this might be your +first release, it's a good idea to keep to the `minor` release. + The `minor` option to the publish command tells apm to increment the second digit of the version before publishing so the published version will be `0.1.0` and the Git tag created will be `v0.1.0`. -In the future you can run `apm publish major` to publish the `1.0.0` version but -since this was the first version being published it is a good idea to start -with a minor release. +The `patch` option to the publish command tells apm to increment the third +digit of the version before publishing so the published version will be `0.0.1` +and the Git tag created will be `v0.0.1`. ### Further Reading