Skip to content

Commit 132e22e

Browse files
committed
location of gbxml and update instructions
1 parent 2eef3dd commit 132e22e

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

BuildingSync.xsd

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<?xml version="1.0" encoding="UTF-8"?>
22
<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">
3-
<xs:import namespace="http://www.gbxml.org/schema" schemaLocation="https://github.com/BuildingSync/schema/releases/download/v2.4.0/GreenBuildingXML_Ver6.01.xsd"/>
3+
<xs:import namespace="http://www.gbxml.org/schema" schemaLocation="https://github.com/BuildingSync/schema/releases/download/v2.3.0/GreenBuildingXML_Ver6.01.xsd"/>
44
<xs:annotation>
55
<xs:documentation>BuildingSync Schema - Version 2.4.0</xs:documentation>
66
<xs:documentation xmlns="http://www.w3.org/1999/xhtml">

docs/release_instructions.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ git tag -a v<version> -m "<message>" [SHA]
3030
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.
3131
```bash
3232
# push the tag
33-
git push origin
33+
git push --tags origin
3434
```
3535

3636
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.

0 commit comments

Comments
 (0)