-
Notifications
You must be signed in to change notification settings - Fork 47
Fix windows/linux CI and document release process #141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
samhill303
wants to merge
11
commits into
main
Choose a base branch
from
sh/release-docs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
9d34f51
Workflow cleanup and release doc
samhill303 da3e1a7
Re-enable Windows and Linux native tests on matching hosts
samhill303 2deb2d6
Point setup-msys2 at the runner's preinstalled MSYS2 so sqlite3 is fi…
samhill303 e7d3e90
Don't install extra toolchain
samhill303 16113fc
Normalize forward slashes in the Windows File path handling
samhill303 1c91a86
Focus on windows for now
samhill303 56d8298
Ignore broken tests. Revert logic changes
samhill303 c0deb98
Suppress Linux linker error
samhill303 f22b3f5
Re-enable platforms
samhill303 4e40ffe
Organize workflow steps
samhill303 cd1baca
Merge branch 'sh/enable-native-tests' into sh/release-docs
samhill303 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,67 @@ | ||
| # Releasing | ||
|
|
||
| SQLiter publishes `co.touchlab:sqliter-driver` to Maven Central. Releases are cut by pushing a release | ||
| tag. | ||
|
|
||
| ## Conventions | ||
|
|
||
| - Tags are the bare version, no `v` prefix — `1.4.0`, not `v1.4.0`. | ||
| - The tag and `VERSION_NAME` must be identical. | ||
| - `main` sits on a `-SNAPSHOT` between releases. | ||
|
|
||
| ## Choosing the version | ||
|
|
||
| Standard semver against the published API surface: | ||
|
|
||
| - **Patch** — bug fixes, no public declarations added or changed. | ||
| - **Minor** — public declarations added. | ||
| - **Major** — public declarations removed or changed incompatibly. | ||
|
|
||
| ## Releasing | ||
|
|
||
| Steps 1–6 are local. Nothing is published until you push the tag in step 7. | ||
|
|
||
| 1. **Confirm the working tree is clean and `main` is current.** | ||
| 2. **Set the release version** in `gradle.properties`: | ||
|
|
||
| ``` | ||
| VERSION_NAME=X.Y.Z | ||
| ``` | ||
|
|
||
| 3. **Commit.** | ||
|
|
||
| ```bash | ||
| git commit -am "Prepare version X.Y.Z" | ||
| ``` | ||
|
|
||
| 4. **Tag that commit.** | ||
|
|
||
| ```bash | ||
| git tag -a X.Y.Z -m "Version X.Y.Z" | ||
| ``` | ||
|
|
||
| 5. **Set the next development version.** Bump the patch and re-add the suffix in | ||
| `gradle.properties`: | ||
|
|
||
| ``` | ||
| VERSION_NAME=<next patch>-SNAPSHOT | ||
| ``` | ||
|
|
||
| So releasing `1.4.1` leaves `main` on `VERSION_NAME=1.4.2-SNAPSHOT`. | ||
|
|
||
| 6. **Commit.** | ||
|
|
||
| ```bash | ||
| git commit -am "Prepare next development version" | ||
| ``` | ||
|
|
||
| 7. **Push the branch first, then the tag.** Pushing the tag triggers the release, so push it last: | ||
|
|
||
| ```bash | ||
| git push origin main | ||
| git push origin X.Y.Z | ||
| ``` | ||
|
|
||
| Pushing requires bypassing main branch protections, if you're not set up to do this, you probably shouldn't be | ||
| publishing anyway | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems that is easy to miss one step and end with an invalid release or a wrong version on the main branch. It would be nice to have some kind of script to automate this.