location of gbxml and update instructions

BuildingSync · Sep 30, 2021 · 132e22e · 132e22e
1 parent 2eef3dd
commit 132e22e
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/BuildingSync.xsd b/BuildingSync.xsd
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:auc="http://buildingsync.net/schemas/bedes-auc/2019" xmlns:gbxml="http://www.gbxml.org/schema" targetNamespace="http://buildingsync.net/schemas/bedes-auc/2019" elementFormDefault="qualified" attributeFormDefault="unqualified" version="2.4.0">
-  <xs:import namespace="http://www.gbxml.org/schema" schemaLocation="https://github.com/BuildingSync/schema/releases/download/v2.4.0/GreenBuildingXML_Ver6.01.xsd"/>
+  <xs:import namespace="http://www.gbxml.org/schema" schemaLocation="https://github.com/BuildingSync/schema/releases/download/v2.3.0/GreenBuildingXML_Ver6.01.xsd"/>
   <xs:annotation>
     <xs:documentation>BuildingSync Schema - Version 2.4.0</xs:documentation>
     <xs:documentation xmlns="http://www.w3.org/1999/xhtml">

diff --git a/docs/release_instructions.md b/docs/release_instructions.md
@@ -30,7 +30,7 @@ git tag -a v<version> -m "<message>" [SHA]
 Where `v<version>` is a valid [semantic version](https://semver.org/) (e.g., `v1.2.3` or `v1.2.3-pr.1`) and `<message>` is the tagging message (e.g. "First official release"). See [Versioning](versioning.md) for more information.
 ```bash
 # push the tag
-git push origin 
+git push --tags origin 
 ```
 
 This should trigger a GitHub workflow for building and publishing the release. If publishing a pre-release, you are done. Otherwise, once the release has been successfully published on GitHub, continue.