diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8bfdf6a31c7..4ca403c1742 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,586 +1,13 @@
 # Changelog
 
-## v1.2.0-rc2 - 2024-05-27
-
-### Bug fixes
-
-- Fixed a bug where the formatter would incorrectly move comments at the start
-  of an anonymous function to the end of the arguments.
-  ([Ameen Radwan](https://github.com/Acepie))
-
-- Fixed a bug where the formatter would not indent a multiline function used
-  in a pipeline.
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- Fixed a bug where the compiler would raise a warning for matching on a literal
-  value if the case expression is used just for its guards.
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- Fixed a bug where not all the analysis errors would be presented to the
-  programmer. ([Louis Pilfold](https://github.com/lpil))
-
-## v1.2.0-rc1 - 2024-05-23
+## Unreleased
 
 ### Build tool
 
-- A helpful error message is now shown if the `manifest.toml` file has been
-  edited to be invalid in some way.
-
-  ```
-  error: Corrupt manifest.toml
-
-  The `manifest.toml` file is corrupt.
-
-  Hint: Please run `gleam update` to fix it.
-  ```
-
-  ([zahash](https://github.com/zahash))
-
-- The error message shown when unable to find package versions that satisfy all
-  the version constraints specified for a project's dependencies has been
-  greatly improved.
-
-  ```
-  error: Dependency resolution failed
-
-  An error occurred while determining what dependency packages and
-  versions should be downloaded.
-  The error from the version resolver library was:
-
-  Unable to find compatible versions for the version constraints in your
-  gleam.toml. The conflicting packages are:
-
-  - hellogleam
-  - lustre_dev_tools
-  - glint
-  ```
-
-  ([zahash](https://github.com/zahash))
-
-- A link to the package on Hex is no longer auto-added to the HTML documentation
-  when building them locally. It is still added when publishing to Hex.
-  ([Pi-Cla](https://github.com/Pi-Cla))
-
-- An error is now emitted when compiling to Erlang and there is a Gleam module
-  that would overwrite a built-in Erlang/OTP module, causing cryptic errors and
-  crashes.
-  ([Louis Pilfold](https://github.com/lpil))
-
-  ```
-  error: Erlang module name collision
-
-  The module `src/code.gleam` compiles to an Erlang module named `code`.
-
-  By default Erlang includes a module with the same name so if we were to
-  compile and load your module it would overwrite the Erlang one, potentially
-  causing confusing errors and crashes.
-
-  Hint: Rename this module and try again.
-  ```
-
-- New subcommand `gleam hex revert` added.
-
-  - You can specify the options like this:
-    `gleam hex revert --package gling --version 1.2.3`
-  - A new package can be reverted or updated within 24 hours of it's initial
-    publish, a new version of an existing package can be reverted or updated
-    within one hour.
-  - You could already update packages even before this release by running:
-    `gleam publish` again.
-
-  ([Pi-Cla](https://github.com/Pi-Cla))
-
-- When the user tries to replace a release without the `--replace` flag
-  the error message now mentions the lack of a `--replace` flag.
-
-  ```
-  error: Version already published
-
-  Version v1.0.0 has already been published.
-  This release has been recently published so you can replace it
-  or you can publish it using a different version number
-
-  Hint: Please add the --replace flag if you want to replace the release.
-  ```
-
-  ([Pi-Cla](https://github.com/Pi-Cla))
-
 ### Compiler
 
-- The compiler will now raise a warning for `let assert` assignments where the
-  assertion is redundant.
-
-  ```
-  warning: Redundant assertion
-    ┌─ /home/lucy/src/app/src/app.gleam:4:7
-    │
-  4 │   let assert x = get_name()
-    │       ^^^^^^ You can remove this
-
-  This assertion is redundant since the pattern covers all possibilities.
-  ```
-
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- Empty case expressions are no longer parse errors and will instead be
-  exhaustiveness errors.
-  ([Race Williams](https://github.com/raquentin))
-
-- Improve error message if importing type using the value import syntax or vice
-  versa.
-
-  ```
-  error: Unknown module field
-    ┌─ /src/one/two.gleam:1:19
-    │
-  1 │ import gleam/one.{One}
-    │                   ^^^ Did you mean `type One`?
-
-  `One` is only a type, it cannot be imported as a value.
-  ```
-
-  ```
-  error: Unknown module type
-    ┌─ /src/one/two.gleam:1:19
-    │
-  1 │ import gleam/two.{type Two}
-    │                   ^^^^^^^^ Did you mean `Two`?
-
-  `Two` is only a value, it cannot be imported as a type.
-  ```
-
-  ([Pi-Cla](https://github.com/Pi-Cla/))
-
-- The compiler will now raise a warning when you try to use `todo` or `panic` as
-  if they were functions: this could previously lead to a confusing behaviour
-  since one might expect the arguments to be printed in the error message.
-  The error message now suggests the correct way to add an error message to
-  `todo` and `panic`.
-
-  ```
-  warning: Todo used as a function
-    ┌─ /src/warning/wrn.gleam:2:16
-    │
-  2 │           todo(1)
-    │                ^
-
-  `todo` is not a function and will crash before it can do anything with
-  this argument.
-
-  Hint: if you want to display an error message you should write
-  `todo as "my error message"`
-  See: https://tour.gleam.run/advanced-features/todo/
-  ```
-
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- Improve error message when something that is not a function appears on the
-  right hand side of `<-` in a `use` expression.
-
-  ```txt
-  error: Type mismatch
-    ┌─ /src/one/two.gleam:2:8
-    │
-  2 │ use <- 123
-    │        ^^^
-
-  In a use expression, there should be a function on the right hand side of
-  `<-`, but this value has type:
-
-      Int
-
-  See: https://tour.gleam.run/advanced-features/use/
-  ```
-
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- Improve error message when a function with the wrong number of arguments
-  appears on the right hand side of `<-` in a `use` expression.
-
-  ```txt
-  error: Incorrect arity
-    ┌─ /src/one/two.gleam:3:8
-    │
-  3 │ use <- func
-    │        ^^^^ Expected no arguments, got 1
-
-  The function on the right of `<-` here takes no arguments.
-  But it has to take at least one argument, a callback function.
-
-  See: https://tour.gleam.run/advanced-features/use/
-  ```
-
-  ```txt
-  error: Incorrect arity
-    ┌─ /src/one/two.gleam:3:8
-    │
-  3 │ use <- f(1, 2)
-    │        ^^^^^^^ Expected 2 arguments, got 3
-
-  The function on the right of `<-` here takes 2 arguments.
-  All the arguments have already been supplied, so it cannot take the
-  `use` callback function as a final argument.
-
-  See: https://tour.gleam.run/advanced-features/use/
-  ```
-
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- Improve error message when the callback function of a `use` expression returns
-  a value with the wrong type.
-  Now the error will point precisely to the last statement and not complain
-  about the whole block saying it has the wrong function type.
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- The compiler will now raise a warning when pattern matching on a literal value
-  like a list, a tuple, integers, strings, etc.
-
-  ```
-  warning: Redundant list
-    ┌─ /src/warning/wrn.gleam:2:14
-    │
-  2 │         case [1, 2] {
-    │              ^^^^^^ You can remove this list wrapper
-
-  Instead of building a list and matching on it, you can match on its
-  contents directly.
-  A case expression can take multiple subjects separated by commas like this:
-
-      case one_subject, another_subject {
-        _, _ -> todo
-      }
-
-  See: https://tour.gleam.run/flow-control/multiple-subjects/
-  ```
-
-  ```
-  warning: Match on a literal value
-    ┌─ /src/warning/wrn.gleam:4:8
-    │
-  4 │   case 1 {
-    │        ^ There's no need to pattern match on this value
-
-  Matching on a literal value is redundant since you can already tell which
-  branch is going to match with this value.
-
-  ```
-
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- The compiler will now continue module analysis when there are errors in top
-  level definitions. This means that when these errors occur the compiler will
-  continue analysing the rest of the code to find other errors and type
-  information.
-
-  When using the build tool this means that the programmer will be shown
-  multiple error messages when there are multiple problems in a module.
-
-  When using the language server multiple error diagnostics will be shown, and
-  the compiler will get updated type information about the code even when there
-  are errors. This should improve the accuracy of feedback and suggestions from
-  the language server as its information about the code will be more up-to-date.
-  ([Ameen Radwan](https://github.com/Acepie)) and
-  ([Louis Pilfold](https://github.com/Acepie))
-
-- An informative error message is now emitted when attempting to use a function
-  from another module in a constant expression. Previously this would result in
-  a cryptic parse error.
-
-  ```
-  error: Syntax error
-    ┌─ /src/parse/error.gleam:3:18
-    │
-  3 │ const wib: Int = wibble(1, "wobble")
-    │                  ^^^^^^^ Functions can only be called within other functions
-  ```
-
-  ([Nino Annighoefer](https://github.com/nino))
-
-- The compiler will now provide more helpful error messages when triple equals
-  are used instead of double equals.
-
-  ```
-  error: Syntax error
-    ┌─ /src/parse/error.gleam:4:37
-    │
-  4 │   [1,2,3] |> list.filter(fn (a) { a === 3 })
-    │                                     ^^^ Did you mean `==`?
-
-  Gleam uses `==` to check for equality between two values.
-  See: https://tour.gleam.run/basics/equality
-  ```
-
-  ([Rabin Gaire](https://github.com/rabingaire))
-
-- The compiler will now raise a warning for unreachable code that comes after
-  a panicking expression.
-
-  ```
-  pub fn main() {
-    panic
-    "unreachable!"
-  }
-  ```
-
-  ```
-  warning: Unreachable code
-    ┌─ /src/warning/wrn.gleam:3:11
-    │
-  3 │    "unreachable!"
-    │    ^^^^^^^^^^^^^^
-
-  This code is unreachable because it comes after a `panic`.
-  ```
-
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- JavaScript external module names may now include the character `@`.
-  ([Louis Pilfold](https://github.com/lpil))
-
 ### Formatter
 
-- Redundant alias names for imported modules are now removed.
-
-  ```gleam
-  import gleam/result as result
-  ```
-
-  is formatted to
-
-  ```gleam
-  import gleam/result
-  ```
-
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- Comments are no longer moved out of constant lists, constant tuples and empty
-  tuples. You can now write this:
-
-  ```gleam
-  const values = [
-    // This is a comment!
-    1, 2, 3
-    // Another comment...
-    11,
-    // And a final one.
-  ]
-  ```
-
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- Comments at the end of an anonymous function are no longer moved out of it.
-  You can now write this:
-
-  ```gleam
-  fn() {
-    todo
-    // A comment here!
-  }
-  ```
-
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- Pipes can now be placed on a single line if they are short enough:
-
-  ```gleam
-  [1, 2, 3] |> list.map(int.to_string) |> string.join(with: "\n")
-  ```
-
-  In addition you can also force the formatter to break a pipe on multiple lines
-  by manually breaking it. This:
-
-  ```gleam
-  [1, 2, 3]
-  // By putting a newline here I'm telling the formatter to split the pipeline
-  |> list.map(int.to_string) |> string.join(with: "\n")
-  ```
-
-  Will turn into this:
-
-  ```gleam
-  [1, 2, 3]
-  |> list.map(int.to_string)
-  |> string.join(with: "\n")
-  ```
-
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- Comments appearing after arguments are no longer moved to a different place.
-  You can now write all of those:
-
-  ```gleam
-  type Record {
-    Record(
-      field: String,
-      // comment_line_1: String,
-      // comment_line_2: String,
-    )
-  }
-  ```
-
-  ```gleam
-  pub fn main() {
-    fn(
-      a,
-      // A comment 2
-    ) {
-      1
-    }
-  }
-  ```
-
-  ```gleam
-  fn main() {
-    let triple = Triple(1, 2, 3)
-    let Triple(
-      a,
-      ..,
-      // comment
-    ) = triple
-    a
-  }
-  ```
-
-  ```gleam
-  type Record {
-    Record(
-      // comment_line_1: String,
-      // comment_line_2: String,
-    )
-  }
-  ```
-
-  ([Mateusz Ledwoń](https://github.com/Axot017))
-
 ### Language Server
 
-- The code action to remove unused imports now removes the entire line is
-  removed if it would otherwise be left blank.
-  ([Milco Kats](https://github.com/katsmil))
-
-- Hover for type annotations is now separate from the thing being annotated.
-  ([Ameen Radwan](https://github.com/Acepie))
-
-- Go to definition now works for direct type annotations.
-  ([Ameen Radwan](https://github.com/Acepie))
-
-- Go to definition now works for import statements.
-  ([Ameen Radwan](https://github.com/Acepie))
-
-- Hover now works for unqualified imports.
-  ([Ameen Radwan](https://github.com/Acepie))
-
-- The language server now detects when the `gleam.toml` config file has changed
-  even if the client does not support watching files. This means that changes to
-  the default target, new dependencies, and other configuration will be
-  automatically detected.
-  ([Louis Pilfold](https://github.com/lpil))
-
-- Completions are now provided for values and types for use in unqualified
-  imports.
-  ([Ameen Radwan](https://github.com/Acepie))
-
-- The character `.` is now advertised as a completion trigger character.
-  ([Louis Pilfold](https://github.com/lpil))
-
-- A new code action has been added to remove redundant tuples around case
-  expression subjects and patterns when possible.
-  ([Nicky Lim](https://github.com/nicklimmm))
-
-  ```
-  case #(x, y) {
-    #(1, 2) -> 0
-    #(_, _) -> 1
-  }
-  ```
-
-  Is rewritten to:
-
-  ```
-  case x, y {
-    1, 2 -> 0
-    _, _ -> 1
-  }
-  ```
-
-- The language server will now register information about code even when there
-  was a type error or similar. This means that the language server will be able
-  to produce some up-to-date information about the project, even when errors are
-  present. This should greatly improve the experience using the language server.
-  ([Louis Pilfold](https://github.com/lpil))
-
 ### Bug Fixes
-
-- Fixed [RUSTSEC-2021-0145](https://rustsec.org/advisories/RUSTSEC-2021-0145) by
-  using Rust's `std::io::IsTerminal` instead of the `atty` library.
-  ([Pi-Cla](https://github.com/Pi-Cla))
-
-- Fixed the generated `mod` property in the Erlang application file when using
-  the `application_start_module` property in `gleam.toml`.
-  ([Alex Manning](https://github.com/rawhat))
-
-- Fixed a confusing error message when using some reserved keywords.
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- Fixed variables in constant expressions not being escaped correctly when
-  exporting to JavaScript.
-  ([PgBiel](https://github.com/PgBiel))
-
-- Fixed a typo when attempting to publish a package with non-Hex dependencies
-  ([inoas](https://github.com/inoas))
-
-- Fixed import completions not appearing in some editors due to the range being
-  longer than the line.
-  ([Ameen Radwan](https://github.com/Acepie))
-
-- Fixed a bug where TypeScript definitions files would use `null` instead of
-  `undefined`.
-  ([Louis Pilfold](https://github.com/lpil))
-
-- Fixed a bug where unreachable infinite cases would not be detected when
-  after a discard or variable pattern.
-  ([Ameen Radwan](https://github.com/Acepie)) and
-  ([Pi-Cla](https://github.com/Pi-Cla))
-
-- Fixed a bug where module imports in guard clauses would not be generated
-  correctly for js target.
-  ([Ameen Radwan](https://github.com/Acepie))
-
-- Fixed a bug where formatting constant lists of tuples would force the
-  tuples to be broken across multiple lines, even when they could fit on a
-  single line.
-  ([Isaac Harris-Holt](https://github.com/isaacharrisholt))
-
-- Fixed a bug where floating points in scientific notation with no trailing
-  zeros would generate invalid Erlang code.
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- Fixed a bug where having utf8 symbols in `gleam.toml`'s description value
-  would result in an HTTP 500 error when running `gleam publish`.
-  ([inoas](https://github.com/inoas))
-
-- Unicode `\u{}` syntax in bit_array string segments now produce valid Erlang
-  unicode characters ([Pi-Cla](https://github.com/Pi-Cla))
-
-- Fixed a bug where using a constant defined in another module that referenced
-  a private function could generate invalid code on the Erlang target.
-  ([Shayan Javani](https://github.com/massivefermion))
-
-- Fixed a bug where the language server would dynamically request the client to
-  watch files even when the client has stated it does not support that.
-  ([Louis Pilfold](https://github.com/lpil))
-
-- Fixed a bug where local path dependencies could be mishandled on Windows.
-  ([Francisco Montanez](https://github.com/Francisco-Montanez))
-
-- Fixed a bug where adding a comment to a case clause would cause it to break
-  on multiple lines.
-  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
-
-- Fixed a bug where pattern matching on a string prefix containing an escape
-  code could generate incorrect Erlang code.
-  ([Nashwan Azhari](https://github.com/aznashwan))
-
-- Fixed a bug where the formatter would produce uneven indentation within
-  multi-line comments at the bottom of case blocks.
-  ([Race Williams](https://github.com/raquentin))
diff --git a/Cargo.lock b/Cargo.lock
index aef6d3fd3a2..54e8a7ccc10 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -802,7 +802,7 @@ checksum = "4271d37baee1b8c7e4b708028c57d816cf9d2434acb33a549475f78c181f6253"
 
 [[package]]
 name = "gleam"
-version = "1.2.0-rc2"
+version = "1.2.0"
 dependencies = [
  "async-trait",
  "base16",
@@ -849,7 +849,7 @@ dependencies = [
 
 [[package]]
 name = "gleam-core"
-version = "1.2.0-rc2"
+version = "1.2.0"
 dependencies = [
  "askama",
  "async-trait",
@@ -900,7 +900,7 @@ dependencies = [
 
 [[package]]
 name = "gleam-wasm"
-version = "1.2.0-rc2"
+version = "1.2.0"
 dependencies = [
  "camino",
  "console_error_panic_hook",
@@ -2238,7 +2238,7 @@ dependencies = [
 
 [[package]]
 name = "test-package-compiler"
-version = "1.2.0-rc2"
+version = "1.2.0"
 dependencies = [
  "camino",
  "gleam-core",
diff --git a/changelog/v1.2.md b/changelog/v1.2.md
new file mode 100644
index 00000000000..5b193a3488f
--- /dev/null
+++ b/changelog/v1.2.md
@@ -0,0 +1,588 @@
+# Changelog
+
+## v1.2.0 - 2024-05-27
+
+## v1.2.0-rc2 - 2024-05-27
+
+### Bug fixes
+
+- Fixed a bug where the formatter would incorrectly move comments at the start
+  of an anonymous function to the end of the arguments.
+  ([Ameen Radwan](https://github.com/Acepie))
+
+- Fixed a bug where the formatter would not indent a multiline function used
+  in a pipeline.
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- Fixed a bug where the compiler would raise a warning for matching on a literal
+  value if the case expression is used just for its guards.
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- Fixed a bug where not all the analysis errors would be presented to the
+  programmer. ([Louis Pilfold](https://github.com/lpil))
+
+## v1.2.0-rc1 - 2024-05-23
+
+### Build tool
+
+- A helpful error message is now shown if the `manifest.toml` file has been
+  edited to be invalid in some way.
+
+  ```
+  error: Corrupt manifest.toml
+
+  The `manifest.toml` file is corrupt.
+
+  Hint: Please run `gleam update` to fix it.
+  ```
+
+  ([zahash](https://github.com/zahash))
+
+- The error message shown when unable to find package versions that satisfy all
+  the version constraints specified for a project's dependencies has been
+  greatly improved.
+
+  ```
+  error: Dependency resolution failed
+
+  An error occurred while determining what dependency packages and
+  versions should be downloaded.
+  The error from the version resolver library was:
+
+  Unable to find compatible versions for the version constraints in your
+  gleam.toml. The conflicting packages are:
+
+  - hellogleam
+  - lustre_dev_tools
+  - glint
+  ```
+
+  ([zahash](https://github.com/zahash))
+
+- A link to the package on Hex is no longer auto-added to the HTML documentation
+  when building them locally. It is still added when publishing to Hex.
+  ([Pi-Cla](https://github.com/Pi-Cla))
+
+- An error is now emitted when compiling to Erlang and there is a Gleam module
+  that would overwrite a built-in Erlang/OTP module, causing cryptic errors and
+  crashes.
+  ([Louis Pilfold](https://github.com/lpil))
+
+  ```
+  error: Erlang module name collision
+
+  The module `src/code.gleam` compiles to an Erlang module named `code`.
+
+  By default Erlang includes a module with the same name so if we were to
+  compile and load your module it would overwrite the Erlang one, potentially
+  causing confusing errors and crashes.
+
+  Hint: Rename this module and try again.
+  ```
+
+- New subcommand `gleam hex revert` added.
+
+  - You can specify the options like this:
+    `gleam hex revert --package gling --version 1.2.3`
+  - A new package can be reverted or updated within 24 hours of it's initial
+    publish, a new version of an existing package can be reverted or updated
+    within one hour.
+  - You could already update packages even before this release by running:
+    `gleam publish` again.
+
+  ([Pi-Cla](https://github.com/Pi-Cla))
+
+- When the user tries to replace a release without the `--replace` flag
+  the error message now mentions the lack of a `--replace` flag.
+
+  ```
+  error: Version already published
+
+  Version v1.0.0 has already been published.
+  This release has been recently published so you can replace it
+  or you can publish it using a different version number
+
+  Hint: Please add the --replace flag if you want to replace the release.
+  ```
+
+  ([Pi-Cla](https://github.com/Pi-Cla))
+
+### Compiler
+
+- The compiler will now raise a warning for `let assert` assignments where the
+  assertion is redundant.
+
+  ```
+  warning: Redundant assertion
+    ┌─ /home/lucy/src/app/src/app.gleam:4:7
+    │
+  4 │   let assert x = get_name()
+    │       ^^^^^^ You can remove this
+
+  This assertion is redundant since the pattern covers all possibilities.
+  ```
+
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- Empty case expressions are no longer parse errors and will instead be
+  exhaustiveness errors.
+  ([Race Williams](https://github.com/raquentin))
+
+- Improve error message if importing type using the value import syntax or vice
+  versa.
+
+  ```
+  error: Unknown module field
+    ┌─ /src/one/two.gleam:1:19
+    │
+  1 │ import gleam/one.{One}
+    │                   ^^^ Did you mean `type One`?
+
+  `One` is only a type, it cannot be imported as a value.
+  ```
+
+  ```
+  error: Unknown module type
+    ┌─ /src/one/two.gleam:1:19
+    │
+  1 │ import gleam/two.{type Two}
+    │                   ^^^^^^^^ Did you mean `Two`?
+
+  `Two` is only a value, it cannot be imported as a type.
+  ```
+
+  ([Pi-Cla](https://github.com/Pi-Cla/))
+
+- The compiler will now raise a warning when you try to use `todo` or `panic` as
+  if they were functions: this could previously lead to a confusing behaviour
+  since one might expect the arguments to be printed in the error message.
+  The error message now suggests the correct way to add an error message to
+  `todo` and `panic`.
+
+  ```
+  warning: Todo used as a function
+    ┌─ /src/warning/wrn.gleam:2:16
+    │
+  2 │           todo(1)
+    │                ^
+
+  `todo` is not a function and will crash before it can do anything with
+  this argument.
+
+  Hint: if you want to display an error message you should write
+  `todo as "my error message"`
+  See: https://tour.gleam.run/advanced-features/todo/
+  ```
+
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- Improve error message when something that is not a function appears on the
+  right hand side of `<-` in a `use` expression.
+
+  ```txt
+  error: Type mismatch
+    ┌─ /src/one/two.gleam:2:8
+    │
+  2 │ use <- 123
+    │        ^^^
+
+  In a use expression, there should be a function on the right hand side of
+  `<-`, but this value has type:
+
+      Int
+
+  See: https://tour.gleam.run/advanced-features/use/
+  ```
+
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- Improve error message when a function with the wrong number of arguments
+  appears on the right hand side of `<-` in a `use` expression.
+
+  ```txt
+  error: Incorrect arity
+    ┌─ /src/one/two.gleam:3:8
+    │
+  3 │ use <- func
+    │        ^^^^ Expected no arguments, got 1
+
+  The function on the right of `<-` here takes no arguments.
+  But it has to take at least one argument, a callback function.
+
+  See: https://tour.gleam.run/advanced-features/use/
+  ```
+
+  ```txt
+  error: Incorrect arity
+    ┌─ /src/one/two.gleam:3:8
+    │
+  3 │ use <- f(1, 2)
+    │        ^^^^^^^ Expected 2 arguments, got 3
+
+  The function on the right of `<-` here takes 2 arguments.
+  All the arguments have already been supplied, so it cannot take the
+  `use` callback function as a final argument.
+
+  See: https://tour.gleam.run/advanced-features/use/
+  ```
+
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- Improve error message when the callback function of a `use` expression returns
+  a value with the wrong type.
+  Now the error will point precisely to the last statement and not complain
+  about the whole block saying it has the wrong function type.
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- The compiler will now raise a warning when pattern matching on a literal value
+  like a list, a tuple, integers, strings, etc.
+
+  ```
+  warning: Redundant list
+    ┌─ /src/warning/wrn.gleam:2:14
+    │
+  2 │         case [1, 2] {
+    │              ^^^^^^ You can remove this list wrapper
+
+  Instead of building a list and matching on it, you can match on its
+  contents directly.
+  A case expression can take multiple subjects separated by commas like this:
+
+      case one_subject, another_subject {
+        _, _ -> todo
+      }
+
+  See: https://tour.gleam.run/flow-control/multiple-subjects/
+  ```
+
+  ```
+  warning: Match on a literal value
+    ┌─ /src/warning/wrn.gleam:4:8
+    │
+  4 │   case 1 {
+    │        ^ There's no need to pattern match on this value
+
+  Matching on a literal value is redundant since you can already tell which
+  branch is going to match with this value.
+
+  ```
+
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- The compiler will now continue module analysis when there are errors in top
+  level definitions. This means that when these errors occur the compiler will
+  continue analysing the rest of the code to find other errors and type
+  information.
+
+  When using the build tool this means that the programmer will be shown
+  multiple error messages when there are multiple problems in a module.
+
+  When using the language server multiple error diagnostics will be shown, and
+  the compiler will get updated type information about the code even when there
+  are errors. This should improve the accuracy of feedback and suggestions from
+  the language server as its information about the code will be more up-to-date.
+  ([Ameen Radwan](https://github.com/Acepie)) and
+  ([Louis Pilfold](https://github.com/Acepie))
+
+- An informative error message is now emitted when attempting to use a function
+  from another module in a constant expression. Previously this would result in
+  a cryptic parse error.
+
+  ```
+  error: Syntax error
+    ┌─ /src/parse/error.gleam:3:18
+    │
+  3 │ const wib: Int = wibble(1, "wobble")
+    │                  ^^^^^^^ Functions can only be called within other functions
+  ```
+
+  ([Nino Annighoefer](https://github.com/nino))
+
+- The compiler will now provide more helpful error messages when triple equals
+  are used instead of double equals.
+
+  ```
+  error: Syntax error
+    ┌─ /src/parse/error.gleam:4:37
+    │
+  4 │   [1,2,3] |> list.filter(fn (a) { a === 3 })
+    │                                     ^^^ Did you mean `==`?
+
+  Gleam uses `==` to check for equality between two values.
+  See: https://tour.gleam.run/basics/equality
+  ```
+
+  ([Rabin Gaire](https://github.com/rabingaire))
+
+- The compiler will now raise a warning for unreachable code that comes after
+  a panicking expression.
+
+  ```
+  pub fn main() {
+    panic
+    "unreachable!"
+  }
+  ```
+
+  ```
+  warning: Unreachable code
+    ┌─ /src/warning/wrn.gleam:3:11
+    │
+  3 │    "unreachable!"
+    │    ^^^^^^^^^^^^^^
+
+  This code is unreachable because it comes after a `panic`.
+  ```
+
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- JavaScript external module names may now include the character `@`.
+  ([Louis Pilfold](https://github.com/lpil))
+
+### Formatter
+
+- Redundant alias names for imported modules are now removed.
+
+  ```gleam
+  import gleam/result as result
+  ```
+
+  is formatted to
+
+  ```gleam
+  import gleam/result
+  ```
+
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- Comments are no longer moved out of constant lists, constant tuples and empty
+  tuples. You can now write this:
+
+  ```gleam
+  const values = [
+    // This is a comment!
+    1, 2, 3
+    // Another comment...
+    11,
+    // And a final one.
+  ]
+  ```
+
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- Comments at the end of an anonymous function are no longer moved out of it.
+  You can now write this:
+
+  ```gleam
+  fn() {
+    todo
+    // A comment here!
+  }
+  ```
+
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- Pipes can now be placed on a single line if they are short enough:
+
+  ```gleam
+  [1, 2, 3] |> list.map(int.to_string) |> string.join(with: "\n")
+  ```
+
+  In addition you can also force the formatter to break a pipe on multiple lines
+  by manually breaking it. This:
+
+  ```gleam
+  [1, 2, 3]
+  // By putting a newline here I'm telling the formatter to split the pipeline
+  |> list.map(int.to_string) |> string.join(with: "\n")
+  ```
+
+  Will turn into this:
+
+  ```gleam
+  [1, 2, 3]
+  |> list.map(int.to_string)
+  |> string.join(with: "\n")
+  ```
+
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- Comments appearing after arguments are no longer moved to a different place.
+  You can now write all of those:
+
+  ```gleam
+  type Record {
+    Record(
+      field: String,
+      // comment_line_1: String,
+      // comment_line_2: String,
+    )
+  }
+  ```
+
+  ```gleam
+  pub fn main() {
+    fn(
+      a,
+      // A comment 2
+    ) {
+      1
+    }
+  }
+  ```
+
+  ```gleam
+  fn main() {
+    let triple = Triple(1, 2, 3)
+    let Triple(
+      a,
+      ..,
+      // comment
+    ) = triple
+    a
+  }
+  ```
+
+  ```gleam
+  type Record {
+    Record(
+      // comment_line_1: String,
+      // comment_line_2: String,
+    )
+  }
+  ```
+
+  ([Mateusz Ledwoń](https://github.com/Axot017))
+
+### Language Server
+
+- The code action to remove unused imports now removes the entire line is
+  removed if it would otherwise be left blank.
+  ([Milco Kats](https://github.com/katsmil))
+
+- Hover for type annotations is now separate from the thing being annotated.
+  ([Ameen Radwan](https://github.com/Acepie))
+
+- Go to definition now works for direct type annotations.
+  ([Ameen Radwan](https://github.com/Acepie))
+
+- Go to definition now works for import statements.
+  ([Ameen Radwan](https://github.com/Acepie))
+
+- Hover now works for unqualified imports.
+  ([Ameen Radwan](https://github.com/Acepie))
+
+- The language server now detects when the `gleam.toml` config file has changed
+  even if the client does not support watching files. This means that changes to
+  the default target, new dependencies, and other configuration will be
+  automatically detected.
+  ([Louis Pilfold](https://github.com/lpil))
+
+- Completions are now provided for values and types for use in unqualified
+  imports.
+  ([Ameen Radwan](https://github.com/Acepie))
+
+- The character `.` is now advertised as a completion trigger character.
+  ([Louis Pilfold](https://github.com/lpil))
+
+- A new code action has been added to remove redundant tuples around case
+  expression subjects and patterns when possible.
+  ([Nicky Lim](https://github.com/nicklimmm))
+
+  ```
+  case #(x, y) {
+    #(1, 2) -> 0
+    #(_, _) -> 1
+  }
+  ```
+
+  Is rewritten to:
+
+  ```
+  case x, y {
+    1, 2 -> 0
+    _, _ -> 1
+  }
+  ```
+
+- The language server will now register information about code even when there
+  was a type error or similar. This means that the language server will be able
+  to produce some up-to-date information about the project, even when errors are
+  present. This should greatly improve the experience using the language server.
+  ([Louis Pilfold](https://github.com/lpil))
+
+### Bug Fixes
+
+- Fixed [RUSTSEC-2021-0145](https://rustsec.org/advisories/RUSTSEC-2021-0145) by
+  using Rust's `std::io::IsTerminal` instead of the `atty` library.
+  ([Pi-Cla](https://github.com/Pi-Cla))
+
+- Fixed the generated `mod` property in the Erlang application file when using
+  the `application_start_module` property in `gleam.toml`.
+  ([Alex Manning](https://github.com/rawhat))
+
+- Fixed a confusing error message when using some reserved keywords.
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- Fixed variables in constant expressions not being escaped correctly when
+  exporting to JavaScript.
+  ([PgBiel](https://github.com/PgBiel))
+
+- Fixed a typo when attempting to publish a package with non-Hex dependencies
+  ([inoas](https://github.com/inoas))
+
+- Fixed import completions not appearing in some editors due to the range being
+  longer than the line.
+  ([Ameen Radwan](https://github.com/Acepie))
+
+- Fixed a bug where TypeScript definitions files would use `null` instead of
+  `undefined`.
+  ([Louis Pilfold](https://github.com/lpil))
+
+- Fixed a bug where unreachable infinite cases would not be detected when
+  after a discard or variable pattern.
+  ([Ameen Radwan](https://github.com/Acepie)) and
+  ([Pi-Cla](https://github.com/Pi-Cla))
+
+- Fixed a bug where module imports in guard clauses would not be generated
+  correctly for js target.
+  ([Ameen Radwan](https://github.com/Acepie))
+
+- Fixed a bug where formatting constant lists of tuples would force the
+  tuples to be broken across multiple lines, even when they could fit on a
+  single line.
+  ([Isaac Harris-Holt](https://github.com/isaacharrisholt))
+
+- Fixed a bug where floating points in scientific notation with no trailing
+  zeros would generate invalid Erlang code.
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- Fixed a bug where having utf8 symbols in `gleam.toml`'s description value
+  would result in an HTTP 500 error when running `gleam publish`.
+  ([inoas](https://github.com/inoas))
+
+- Unicode `\u{}` syntax in bit_array string segments now produce valid Erlang
+  unicode characters ([Pi-Cla](https://github.com/Pi-Cla))
+
+- Fixed a bug where using a constant defined in another module that referenced
+  a private function could generate invalid code on the Erlang target.
+  ([Shayan Javani](https://github.com/massivefermion))
+
+- Fixed a bug where the language server would dynamically request the client to
+  watch files even when the client has stated it does not support that.
+  ([Louis Pilfold](https://github.com/lpil))
+
+- Fixed a bug where local path dependencies could be mishandled on Windows.
+  ([Francisco Montanez](https://github.com/Francisco-Montanez))
+
+- Fixed a bug where adding a comment to a case clause would cause it to break
+  on multiple lines.
+  ([Giacomo Cavalieri](https://github.com/giacomocavalieri))
+
+- Fixed a bug where pattern matching on a string prefix containing an escape
+  code could generate incorrect Erlang code.
+  ([Nashwan Azhari](https://github.com/aznashwan))
+
+- Fixed a bug where the formatter would produce uneven indentation within
+  multi-line comments at the bottom of case blocks.
+  ([Race Williams](https://github.com/raquentin))
diff --git a/compiler-cli/Cargo.toml b/compiler-cli/Cargo.toml
index 7a93819c821..8140050a5c5 100644
--- a/compiler-cli/Cargo.toml
+++ b/compiler-cli/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "gleam"
-version = "1.2.0-rc2"
+version = "1.2.0"
 authors = ["Louis Pilfold <louis@lpil.uk>"]
 edition = "2021"
 license-file = "LICENCE"
diff --git a/compiler-core/Cargo.toml b/compiler-core/Cargo.toml
index 96c7befba0d..b55cef62a50 100644
--- a/compiler-core/Cargo.toml
+++ b/compiler-core/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "gleam-core"
-version = "1.2.0-rc2"
+version = "1.2.0"
 authors = ["Louis Pilfold <louis@lpil.uk>"]
 edition = "2021"
 license-file = "LICENCE"
diff --git a/compiler-wasm/Cargo.toml b/compiler-wasm/Cargo.toml
index ecbed19dd47..9cceb115317 100644
--- a/compiler-wasm/Cargo.toml
+++ b/compiler-wasm/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "gleam-wasm"
-version = "1.2.0-rc2"
+version = "1.2.0"
 authors = ["Louis Pilfold <louis@lpil.uk>"]
 edition = "2021"
 license-file = "LICENCE"
diff --git a/test-package-compiler/Cargo.toml b/test-package-compiler/Cargo.toml
index acead84caa4..be87ecedb78 100644
--- a/test-package-compiler/Cargo.toml
+++ b/test-package-compiler/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "test-package-compiler"
-version = "1.2.0-rc2"
+version = "1.2.0"
 authors = ["Louis Pilfold <louis@lpil.uk>"]
 edition = "2021"
 license-file = "LICENCE"