Dropping -dev from version

Author: akoutmos

RELEASE.md

@@ -6,66 +6,66 @@ releasing is a bit more involved than it would be otherwise.
 
 1. Pick the new release `version`.
 
-    * We follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-    * Should be the current version in `mix.exs` with `-dev` removed.
+   - We follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+   - Should be the current version in `mix.exs` with `-dev` removed.
 
-1. Begin drafting a new release.
+2. Begin drafting a new release.
 
-    1. Go to https://github.com/elixir-explorer/explorer/releases.
-    1. Click "Draft a new release".
-    1. Under "Select tag", set the tag to `v{version}`, e.g. `v0.11.0`.
-    1. Keep the target branch as `main`.
-    1. Click "Generate release notes".
-    1. Stop here. Wait until later to actually publish the release.
+   1. Go to https://github.com/elixir-explorer/explorer/releases.
+   2. Click "Draft a new release".
+   3. Under "Select tag", set the tag to `v{version}`, e.g. `v0.11.0`.
+   4. Keep the target branch as `main`.
+   5. Click "Generate release notes".
+   6. Stop here. Wait until later to actually publish the release.
 
-1. Open a PR with any changes needed for the release. Must include:
+3. Open a PR with any changes needed for the release. Must include:
 
-    * Updating the `version` in `mix.exs`
-    * Updating the `version` in any other files that reference it, like
-        * `README.md` (multiple places)
-        * `notebooks/exploring_explorer.livemd`
-    * Updating the `CHANGELOG.md` to reflect the release
-        * Use the generated release notes from earlier as a starting point.
-        * Edit the entries to follow the format from
-          https://keepachangelog.com/en/1.1.0/.
+   - Updating the `version` in `mix.exs`
+   - Updating the `version` in any other files that reference it, like
+     - `README.md` (multiple places)
+     - `notebooks/exploring_explorer.livemd`
+   - Updating the `CHANGELOG.md` to reflect the release
+     - Use the generated release notes from earlier as a starting point.
+     - Edit the entries to follow the format from
+       https://keepachangelog.com/en/1.1.0/.
 
-1. Merge the PR.
+4. Merge the PR.
 
-1. On the release draft page, click "Publish release".
+5. On the release draft page, click "Publish release".
 
-1. Publishing the release will kick off the "Build precompiled NIFs" GitHub
+6. Publishing the release will kick off the "Build precompiled NIFs" GitHub
    Action. Wait for this to complete.
 
-    * It usually takes around 40-60 minutes.
+   - It usually takes around 40-60 minutes.
 
-1. Generate the artifact checksums.
+7. Generate the artifact checksums.
 
-    1. Go to your local version of Explorer.
-    1. Ensure you have the latest version of `main` (post PR merge).
-    1. Remove any intermediate builds by running:
-        ```
-        rm -rf native/explorer/target
-        ```
-    1. Download all the artifacts and generate the checksums:
-        ```
-        EXPLORER_BUILD=true mix rustler_precompiled.download Explorer.PolarsBackend.Native --all --print
-        ```
+   1. Go to your local version of Explorer.
+   2. Ensure you have the latest version of `main` (post PR merge).
+   3. Remove any intermediate builds by running:
+      ```
+      rm -rf native/explorer/target
+      ```
+   4. Download all the artifacts and generate the checksums:
+      ```
+      EXPLORER_BUILD=true mix rustler_precompiled.download Explorer.PolarsBackend.Native --all --print
+      ```
 
-1. Paste the checksums into the release description on GitHub.
+8. Paste the checksums into the release description on GitHub.
 
-    1. Go to the release published earlier at the top of
-       https://github.com/elixir-explorer/explorer/releases.
-    1. Click the "Edit" pencil icon.
-    1. At the bottom, paste the SHA256 contents under the heading "SHA256 of the
-       artifacts" (ensure the contents are formatted to look like code).
+   1. Go to the release published earlier at the top of
+      https://github.com/elixir-explorer/explorer/releases.
+   2. Click the "Edit" pencil icon.
+   3. At the bottom, paste the SHA256 contents under the heading "SHA256 of the
+      artifacts" (ensure the contents are formatted to look like code).
 
-1. Run `mix hex.publish`.
+9. Run `mix hex.publish`.
 
-    1. Double check the dependencies and files.
-    1. Enter "Y" to confirm.
-    1. Discard the auto-generated `.exs` file beginning with `checksum`.
+   1. Double check the dependencies and files.
+   2. Enter "Y" to confirm.
+   3. Discard the auto-generated `.exs` file beginning with `checksum`.
 
-1. Bump the version in the `mix.exs` and add the `-dev` flag to the end.
+10. Bump the version in the `mix.exs` and add the `-dev` flag to the end.
 
-    * Example: `0.11.0` to `0.11.1-dev`.
-    * Can either open up a PR or push directly to `main`.
+- Example: `0.11.0` to `0.11.1-dev`.
+- Can either open up a PR or push directly to `main`.

mix.exs

@@ -2,7 +2,7 @@ defmodule Explorer.MixProject do
   use Mix.Project
 
   @source_url "https://github.com/elixir-nx/explorer"
-  @version "0.12.0-dev"
+  @version "0.12.0"
   @dev? String.ends_with?(@version, "-dev")
   @force_build? System.get_env("EXPLORER_BUILD") in ["1", "true"]