Bump 1.0.0

Author: palkan

CHANGELOG.md

@@ -1,13 +1,11 @@
 # Change log
 
-## master (unreleased)
+## 1.0.0 (2020-11-09)
 
 - Add `--name` option to model generator to specify the migration name. ([@palkan][])
 
 When you update Logidze installation for a model multiple times, you might hit the `DuplicateMigrationNameError` (see [#167](https://github.com/palkan/logidze/issues/167)).
 
-## 1.0.0.rc1 (2020-09-01)
-
 - Add `.with_full_snapshot` to add full snapshots to the log instead of diffs. ([@palkan][])
 
 Useful in combination with `.without_logging`: first, you perform multiple updates without logging, then

README.md

@@ -10,8 +10,6 @@ Logidze provides tools for logging DB records changes when using PostgreSQL (>=9
 Logidze allows you to create a DB-level log (using triggers) and gives you an API to browse this log.
 The log is stored with the record itself in JSONB column. No additional tables required.
 
-**❗️ IMPORTANT:** This page contains documentation for the upcoming v1.0. For the latest release documentation see the [0-stable branch](https://github.com/palkan/logidze/tree/0-stable). If you're just starting with Logidze, we recommend using the latest release candidate (`1.0.0.rc1`).
-
 🤔 [How is Logidze pronounced?](https://github.com/palkan/logidze/issues/73)
 
 Other requirements:
@@ -56,7 +54,7 @@ Other requirements:
 Add Logidze to your application's Gemfile:
 
 ```ruby
-gem "logidze", "1.0.0.rc1"
+gem "logidze", "~> 1.0.0"
 ```
 
 Install required DB extensions and create trigger function:

lib/logidze/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Logidze
-  VERSION = "1.0.0.rc1"
+  VERSION = "1.0.0"
 end