Merge pull request #461 from IntersectMBO/lucsanszky/update-changelogs

Update `CHANGELOG`s post-release

RELEASING.md

@@ -148,19 +148,19 @@ CHaP. (TODO: implement a script that lists all of the package that fit the above
 #### Release to CHaP
 
 1. Follow the [CHaP release
-   instructions](https://github.com/input-output-hk/cardano-haskell-packages#-from-github)
+   instructions](https://github.com/intersectmbo/cardano-haskell-packages#-from-github)
 
    For example:
 
    ```shell
-   $ ./scripts/add-from-github.sh https://github.com/input-output-hk/cardano-base libs/cardano-crypto-class deadbeef...
+   $ ./scripts/add-from-github.sh https://github.com/intersectmbo/cardano-base deadbeef libs/cardano-crypto-class ...
    ```
    It is important to supply a commit SHA instead of a branch name.
 
-2. Create and merge a PR to https://github.com/input-output-hk/cardano-haskell-packages
+2. Create and merge a PR to https://github.com/intersectmbo/cardano-haskell-packages
    with the release(s). In case that a current release causes breakage on some downstream
    package due to that package lacking upper bounds, you will require to [add a revision
-   for that package](https://github.com/input-output-hk/cardano-haskell-packages#how-to-add-a-new-package-metadata-revision) that fixes the bounds in the same PR as the release. Also it is
+   for that package](https://github.com/intersectmbo/cardano-haskell-packages#how-to-add-a-new-package-metadata-revision) that fixes the bounds in the same PR as the release. Also it is
    necessary to notify the maintainers of the package via a bug report or a PR with a fix.
 
 3. Once the PR is merged then create a git tag with the same version for the same git SHA
@@ -241,7 +241,7 @@ Currently there are no such packages that fit the criteria below, but this could
 the future.
 
 We release all of the packages in this repo to [CHaP (Cardano Haskell
-Packages)](https://github.com/input-output-hk/cardano-haskell-packages). However, packages
+Packages)](https://github.com/intersectmbo/cardano-haskell-packages). However, packages
 can be added to the repo that are either used for testing, debugging or benchmarking and
 do not deserve to be released into the World. They will neither be released nor
 versioned. Bounds on the local dependencies do not need to be updated for such packages,

cardano-slotting/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog for `cardano-slotting`
 
+## 0.2.0.1
+
+*
+
 ## 0.2.0.0
 
 * Add `EpochInterval` and `addEpochInterval` from `cardano-ledger`.

cardano-strict-containers/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog for `cardano-strict-containers`
 
+# 0.1.3.1
+
+*
+
 # 0.1.3.0
 
 * Added `IsList` instance for `StrictSeq`