Skip to content

Commit 50ac642

Browse files
committed
Release v0.1.1
1 parent 70b54d8 commit 50ac642

2 files changed

Lines changed: 29 additions & 2 deletions

File tree

.github/workflows/release.yml

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -70,6 +70,20 @@ jobs:
7070
test -n "$TOML_VERSION"
7171
test "$VERSION" = "$TOML_VERSION"
7272
73+
- name: Setup Erlang + Gleam
74+
uses: erlef/setup-beam@v1
75+
with:
76+
otp-version: "27"
77+
gleam-version: "1.17.0"
78+
rebar3-version: "3"
79+
80+
- name: Publish to Hex
81+
if: ${{ secrets.HEXPM_API_KEY != '' }}
82+
env:
83+
HEXPM_API_KEY: ${{ secrets.HEXPM_API_KEY }}
84+
run: |
85+
printf "I am not using semantic versioning\n" | gleam publish
86+
7387
- uses: actions/download-artifact@v4
7488
with:
7589
path: dist

RELEASING.md

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,10 +54,23 @@ git push origin main --tags
5454

5555
## 2) Publish the package to Hex / Gleam Packages
5656

57-
On the machine where you have Hex credentials configured:
57+
### Option A: Publish from CI (recommended)
58+
59+
Add these GitHub repository secrets:
60+
61+
- `HEXPM_API_KEY`
62+
63+
Then push the `vX.Y.Z` tag as usual. The `release.yml` workflow publishes to Hex from `ubuntu-latest` before creating the GitHub Release.
64+
65+
### Option B: Publish locally
66+
67+
On a machine where you have Hex credentials configured:
5868

5969
```bash
6070
gleam publish
6171
```
6272

63-
If you are going to use CI to publish, you will need to configure the corresponding token (not included in this repo).
73+
Notes:
74+
75+
- For `0.x.x`, Gleam will ask you to confirm that you are not using semantic versioning.
76+
- On Windows, publishing can fail if your environment blocks symlinks; CI on Linux avoids this.

0 commit comments

Comments
 (0)