Merge pull request #1075 from radiantearth/dev

Dev to master merge for changelog update

.circleci/config.yml

@@ -46,12 +46,8 @@ workflows:
       - test_examples
       - test_docs
       - publish_schemas:
-          requires:
-            - test_examples
           filters:
             tags:
-              # All (future) tags
               only: /^v.*/
             branches:
-              # Only dev branch, not PRs
-              only: dev
+              ignore: /^((?!dev).)*$/

CHANGELOG.md

@@ -8,15 +8,15 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [v1.0.0-rc.2] - 2021-03-30
 
-### Added
-
 ### Changed
 
 - Required properties of type `string` require a minimum length of `1`. ([#1065](https://github.com/radiantearth/stac-spec/pull/1065))
 - `gsd` must be greater than 0. ([#1068](https://github.com/radiantearth/stac-spec/pull/1068))
 
 ### Removed
 
+- The remaining extensions in the spec (EO, Projection, Scientific Citation and View) have been moved out of the core specification, into their own repos in the [stac-extensions](https://github.com/stac-extensions/) GitHub organization. They must now be referred to by their schemas directly - the name shortcuts for them are no longer valid. The concept of the 'named shortcut' also goes away entirely. ([#1070](https://github.com/radiantearth/stac-spec/pull/1070))
+
 ### Fixed
 
 - Collection Assets were specified as required (only in written text, not in JSON Schema), but that was incorrectly copied over from the former `collection-assets` extension. Collection Assets are not required.

catalog-spec/json-schema/catalog-core.json

@@ -22,7 +22,7 @@
         "stac_version": {
           "title": "STAC version",
           "type": "string",
-          "const": "1.0.0-rc.1"
+          "const": "1.0.0-rc.2"
         },
         "stac_extensions": {
           "title": "STAC extensions",

collection-spec/collection-spec.md

@@ -88,7 +88,7 @@ Collection's license(s) as a SPDX [License identifier](https://spdx.org/licenses
 
 #### summaries
 
-Collections are are *strongly recommended* to provide summaries of the values of fields that they can expect from the `properties` 
+Collections are *strongly recommended* to provide summaries of the values of fields that they can expect from the `properties` 
 of STAC Items contained in this Collection. This enables users to get a good sense of what the ranges and potential values of 
 different fields in the Collection are, without to inspect a number of Items (or crawl them exhaustively to get a definitive answer). 
 Summaries help to fully define Collections, especially if they don't link to any Items. They also give clients enough information to 

item-spec/json-schema/item.json

@@ -93,7 +93,7 @@
             "stac_version": {
               "title": "STAC version",
               "type": "string",
-              "const": "1.0.0-rc.1"
+              "const": "1.0.0-rc.2"
             },
             "stac_extensions": {
               "title": "STAC extensions",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "stac-spec",
-  "version": "1.0.0-rc.1",
+  "version": "1.0.0-rc.2",
   "description": "STAC spec helpers to check the spec.",
   "repository": "https://github.com/radiantearth/stac-spec",
   "license": "Apache-2.0",