obsidian-export/.github/workflows/publish-crate.yml

name: Publish to crates.io

on:
  workflow_call:
    inputs:
      plan:
        required: true
        type: string

jobs:
  publish:
    runs-on: ubuntu-latest
    env:
      PLAN: ${{ inputs.plan }}
      CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
    steps:
      - uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332 # v4
      - uses: ./.github/actions/setup-ci
      - run: cargo publish
Use cargo-dist to create release artifacts This will create binaries for more platforms (including ARM builds for MacOS) and installer scripts in addition to just the binaries themselves. 2023-12-03 16:06:02 +03:00			`name: Publish to crates.io`

			`on:`
			`workflow_call:`
			`inputs:`
			`plan:`
			`required: true`
			`type: string`

			`jobs:`
			`publish:`
			`runs-on: ubuntu-latest`
			`env:`
			`PLAN: ${{ inputs.plan }}`
			`CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}`
			`steps:`
Pin dependencies 2024-06-23 15:59:44 +03:00			`- uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332 # v4`
Change release process to use towncrier and delay regenerating README 1. Use [towncrier][1] to generate release notes/CHANGELOG instead of auto-generating it from git commit messages. 2. Move release scripts into a Justfile. 3. Only regenerate the top-level README file when making a release, don't force it to be up to date in between releases. Point 3 helps prevent documentation for unreleased changes from being shown to users on GitHub, which may otherwise be confusing. [1]: https://towncrier.readthedocs.io/en/stable/index.html# 2024-08-04 13:36:11 +03:00			`- uses: ./.github/actions/setup-ci`
Use cargo-dist to create release artifacts This will create binaries for more platforms (including ARM builds for MacOS) and installer scripts in addition to just the binaries themselves. 2023-12-03 16:06:02 +03:00			`- run: cargo publish`