Update version to 0.1.2

This commit is contained in:
BoykoAlex
2018-01-17 15:58:39 -05:00
parent 851f5b29e5
commit f1fa29da8f
7 changed files with 28 additions and 12 deletions

View File

@@ -1,7 +1,7 @@
{
"name": "boot-java",
"main": "./lib/main",
"version": "0.1.2",
"version": "0.1.3",
"description": "Spring Boot support for Atom",
"repository": "https://github.com/spring-projects/atom-boot-java",
"icon": "icon.png",
@@ -25,7 +25,7 @@
"dependencies": {
"atom-package-deps": "^4.6.0",
"download": "^6.2.5",
"pivotal-atom-languageclient-commons": "0.0.18"
"pivotal-atom-languageclient-commons": "0.0.19"
},
"devDependencies": {
"coffeelint": "^1.10.1"

View File

@@ -1,7 +1,7 @@
{
"name": "boot-properties",
"main": "./lib/main",
"version": "0.1.2",
"version": "0.1.3",
"description": "Spring Boot Properties support for Atom",
"repository": "https://github.com/spring-projects/atom-boot-properties",
"icon": "icon.png",
@@ -19,7 +19,7 @@
"dependencies": {
"atom-package-deps": "^4.6.0",
"download": "^6.2.5",
"pivotal-atom-languageclient-commons": "0.0.18"
"pivotal-atom-languageclient-commons": "0.0.19"
},
"devDependencies": {
"coffeelint": "^1.10.1"

View File

@@ -1,7 +1,7 @@
{
"name": "bosh-yaml",
"main": "./lib/main",
"version": "0.1.2",
"version": "0.1.3",
"description": "Provides validation and content assist for various Bosh configuration files",
"repository": "https://github.com/spring-projects/atom-bosh",
"icon": "icon.png",
@@ -19,7 +19,7 @@
"dependencies": {
"atom-package-deps": "^4.6.0",
"download": "^6.2.5",
"pivotal-atom-languageclient-commons": "0.0.18"
"pivotal-atom-languageclient-commons": "0.0.19"
},
"configSchema": {
"bosh": {

View File

@@ -1,7 +1,7 @@
{
"name": "cf-manifest-yaml",
"main": "./lib/main",
"version": "0.1.2",
"version": "0.1.3",
"description": "Cloud Foundry Deployment Manifest YAML support for Atom",
"repository": "https://github.com/spring-projects/atom-cf-manifest-yaml",
"icon": "icon.png",
@@ -19,7 +19,7 @@
"dependencies": {
"atom-package-deps": "^4.6.0",
"download": "^6.2.5",
"pivotal-atom-languageclient-commons": "0.0.18"
"pivotal-atom-languageclient-commons": "0.0.19"
},
"devDependencies": {
"coffeelint": "^1.10.1"

View File

@@ -1,6 +1,6 @@
{
"name": "pivotal-atom-languageclient-commons",
"version": "0.0.18",
"version": "0.0.19",
"description": "Atom language client commons for STS4 language servers",
"repository": "https://github.com/spring-projects/sts4",
"license": "MIT",
@@ -8,7 +8,7 @@
"atom": ">=1.17.0"
},
"dependencies": {
"atom-languageclient": "0.6.7",
"atom-languageclient": "0.8.0",
"decompress": "^4.2.0",
"portfinder": "^1.0.13",
"remote-file-size": "^3.0.3",

View File

@@ -1,7 +1,7 @@
{
"name": "concourse-pipeline-yaml",
"main": "./lib/main",
"version": "0.1.2",
"version": "0.1.3",
"description": "Provides validation and content assist for Concourse CI pipeline and task configuration yml files",
"repository": "https://github.com/spring-projects/atom-concourse",
"icon": "icon.png",
@@ -19,7 +19,7 @@
"dependencies": {
"atom-package-deps": "^4.6.0",
"download": "^6.2.5",
"pivotal-atom-languageclient-commons": "0.0.18"
"pivotal-atom-languageclient-commons": "0.0.19"
},
"devDependencies": {
"coffeelint": "^1.10.1"

View File

@@ -0,0 +1,16 @@
# Development Notes
## Releasing Atom Extension
Before Atom package is released the RC language server `JAR` nneds to be produced. Open [promote-fatjars-to-rc](https://ci.spring.io/teams/tools/pipelines/sts4-master/jobs/promote-fatjars-to-rc/builds/1) task in Concours and kick of the build.
Once the build completes successfully it'd push the update to `properties.json` of the Atom extension with the link to the RC language server `JAR` file
The release process for an STS4 Atom package `X` is to be done with the contents of the release GitHub repository corresponding to the Atom package. Namely: `https://github.com/spring-projects/<X>`
(Example: `atom-bosh` -> Release repo: https://github.com/spring-projects/atom-bosh)
1. Clone the release repository for Atom package `X`
2. Navigate to `X` folder. Examine `package.json`. The version in that file is most likely the one to be published. (Verify tags of the release git repo to verify this)
3. Lets assume it's version `A.B.C` to be publsihed. The same version must be in the `package.json`
4. Execute `git tag vA.B.C`
5. Execute `git push --tags`
6. Execute `apm publish --tag vA.B.C`