Skip to content

Commit 5b64b1d

Browse files
authored
Merge pull request #197 from ducflair/jorgedanisc
Jorgedanisc
2 parents 1089a78 + 0a6533f commit 5b64b1d

5 files changed

Lines changed: 30 additions & 38 deletions

File tree

.github/workflows/release-ducpy.yml

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -76,6 +76,29 @@ jobs:
7676
fi
7777
working-directory: ./packages/ducpy
7878

79+
- name: Install Pyodide build tooling
80+
id: pyodide_tooling
81+
if: steps.release.outputs.status == 'success'
82+
run: |
83+
python -m pip install --upgrade pip
84+
pip install "pyodide-build>=0.29.2"
85+
echo "emscripten_version=$(pyodide config get emscripten_version)" >> $GITHUB_OUTPUT
86+
87+
- name: Setup Emscripten SDK
88+
if: steps.release.outputs.status == 'success'
89+
uses: mymindstorm/setup-emsdk@v14
90+
with:
91+
version: ${{ steps.pyodide_tooling.outputs.emscripten_version }}
92+
93+
- name: Build Pyodide wheel
94+
if: steps.release.outputs.status == 'success'
95+
working-directory: ./packages/ducpy
96+
run: |
97+
TAG=$(git describe --tags --abbrev=0)
98+
VERSION="${TAG#ducpy@}"
99+
echo "Building Pyodide wheel for version ${VERSION}"
100+
SETUPTOOLS_SCM_PRETEND_VERSION="${VERSION}" pyodide build --outdir dist
101+
79102
- name: Upload wheels to GitHub release
80103
if: steps.release.outputs.status == 'success'
81104
env:

packages/ducjs/README.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
1+
# ducjs
2+
13
<p align="center">
24
<br/>
35
<a href="https://duc.ducflair.com" target="_blank"><img width="256px" src="https://raw.githubusercontent.com/ducflair/assets/refs/heads/main/src/duc/duc-extended.png" /></a>
@@ -10,9 +12,6 @@
1012
</p>
1113
</p>
1214

13-
14-
# ducjs
15-
1615
The `ducjs` package offers comprehensive TypeScript types and helper functions to work effortlessly with the `duc` CAD file format. Built with SQLite and optimized for performance, this package enables you to parse, validate, and manipulate `duc` files with ease.
1716

1817
## Documentation

packages/ducpdf/release.config.cjs

Lines changed: 2 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -9,23 +9,8 @@ module.exports = {
99
"packages/ducjs",
1010
"packages/ducrs"
1111
],
12-
// This is the one that controls the version bump (major/minor/patch)
13-
analyzer: {
14-
preset: "conventionalcommits",
15-
parserOpts: {
16-
// Temporarily set to a keyword nobody will use
17-
noteKeywords: ["SKIP_BREAKING_DETECTION"],
18-
},
19-
},
20-
21-
// This controls release notes generation (so "Breaking Changes" sections, etc.)
22-
// If you only change `analyzer`, you might still see BREAKING CHANGE notes in output notes.
23-
notes: {
24-
preset: "conventionalcommits",
25-
parserOpts: {
26-
noteKeywords: ["SKIP_BREAKING_DETECTION"],
27-
},
28-
},
12+
analyzer: { preset: "conventionalcommits" },
13+
notes: { preset: "conventionalcommits" },
2914
},
3015
],
3116
[

packages/ducpy/release.config.cjs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ module.exports = {
1616
"@semantic-release/exec",
1717
{
1818
prepareCmd:
19-
"bun prerelease && sed -i 's/^version = \".*\"$/version = \"${nextRelease.version}\"/' crate/Cargo.toml && bun run build ${nextRelease.version}",
19+
"bun prerelease && sed -i 's/^version = \".*\"$/version = \"${nextRelease.version}\"/' crate/Cargo.toml && SETUPTOOLS_SCM_PRETEND_VERSION=${nextRelease.version} uv build --sdist",
2020
publishCmd: "uv publish --token ${process.env.PYPI_TOKEN} dist/*.tar.gz",
2121
},
2222
],

packages/ducsvg/release.config.cjs

Lines changed: 2 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -10,23 +10,8 @@ module.exports = {
1010
"packages/ducjs",
1111
"packages/ducrs",
1212
],
13-
// This is the one that controls the version bump (major/minor/patch)
14-
analyzer: {
15-
preset: "conventionalcommits",
16-
parserOpts: {
17-
// Temporarily set to a keyword nobody will use
18-
noteKeywords: ["SKIP_BREAKING_DETECTION"],
19-
},
20-
},
21-
22-
// This controls release notes generation (so "Breaking Changes" sections, etc.)
23-
// If you only change `analyzer`, you might still see BREAKING CHANGE notes in output notes.
24-
notes: {
25-
preset: "conventionalcommits",
26-
parserOpts: {
27-
noteKeywords: ["SKIP_BREAKING_DETECTION"],
28-
},
29-
},
13+
analyzer: { preset: "conventionalcommits" },
14+
notes: { preset: "conventionalcommits" },
3015
},
3116
],
3217
[

0 commit comments

Comments
 (0)