addressed ON_RELEASE chores

Author: ijchen

CHANGELOG.md

@@ -1,5 +1,3 @@
-<!-- ON_RELEASE: Add changelog entry for new version and remove this comment -->
-
 # Major Version 1
 
 ## v1.0.0

Cargo.lock

@@ -6,7 +6,7 @@
 
 [package]
 name = "pair"
-version = "0.1.0" # ON_RELEASE: Bump version. Also, do all "ON_RELEASE" tasks
+version = "1.0.0"
 authors = ["Isaac Chen"]
 edition = "2024"
 rust-version = "1.85.0"

Cargo.toml

@@ -12,13 +12,6 @@ You define how to construct a dependent type from a reference to an owning type,
 and [`Pair`] will carefully bundle them together in a safe and freely movable
 self-referential struct.
 
-<!-- ON_RELEASE: for 1.0, permanantly remove this section (and this comment) -->
-# DO NOT USE THIS LIBRARY
-
-As of right now, I have absolutely no idea whether or not this API is sound. You
-should *absolutely not* use this library for anything that matters at this point
-in time.
-
 # Example Usage
 
 A typical use case might look something like this:
@@ -155,5 +148,4 @@ dual licensed as above, without any additional terms or conditions.
 docs.rs documentation links for rendered markdown (ex, on GitHub)
 These are overridden when include_str!(..)'d in lib.rs
 -->
-<!-- ON_RELEASE: the below link(s) should be updated, and this comment removed -->
-[`Pair`]: https://docs.rs/pair/__CRATE_VERSION_HERE__/pair/struct.Pair.html
+[`Pair`]: https://docs.rs/pair/1.0.0/pair/struct.Pair.html

README.md

@@ -1,8 +1,6 @@
 // These markdown links are used to override the docs.rs web links present at
 // the bottom of README.md. These two lists must be kept in sync, or the links
 // included here will be hard-coded links to docs.rs, not relative doc links.
-// ON_RELEASE: the below link(s) should be verified to match the readme, and
-// this "on release" comment removed (the above one should stay).
 //! [`Pair`]: Pair
 #![cfg_attr(any(doc, test), doc = include_str!("../README.md"))]
 #![no_std]