Skip to content

Commit e20880a

Browse files
authored
Update powersync-kotlin to 1.0.0-BETA30 (#38)
* Update powersync-kotlin to BETA30 * Document tag names
1 parent 9333846 commit e20880a

File tree

4 files changed

+8
-3
lines changed

4 files changed

+8
-3
lines changed

CHANGELOG.md

+4
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
# Changelog
22

3+
# 1.0.0-beta.11
4+
5+
* Fix deadlock when `connect()` is called immediately after opening a database.
6+
37
# 1.0.0-Beta.10
48

59
* Added the ability to specify a custom logging implementation

Package.resolved

+2-2
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@
55
"kind" : "remoteSourceControl",
66
"location" : "https://github.com/powersync-ja/powersync-kotlin.git",
77
"state" : {
8-
"revision" : "f306c059580b4c4ee2b36eec3c68f4d5326a454c",
9-
"version" : "1.0.0-BETA29.0"
8+
"revision" : "633a2924f7893f7ebeb064cbcd9c202937673633",
9+
"version" : "1.0.0-BETA30.0"
1010
}
1111
},
1212
{

Package.swift

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ let package = Package(
1717
targets: ["PowerSync"]),
1818
],
1919
dependencies: [
20-
.package(url: "https://github.com/powersync-ja/powersync-kotlin.git", exact: "1.0.0-BETA29.0"),
20+
.package(url: "https://github.com/powersync-ja/powersync-kotlin.git", exact: "1.0.0-BETA30.0"),
2121
.package(url: "https://github.com/powersync-ja/powersync-sqlite-core-swift.git", "0.3.12"..<"0.4.0")
2222
],
2323
targets: [

docs/Release.md

+1
Original file line numberDiff line numberDiff line change
@@ -5,4 +5,5 @@
55
* Confirm every PR you want in the release has been merged into `main`.
66
* Update `CHANGELOG.md` with the changes.
77
* In GitHub actions on GitHub manually run the `Release PowerSync` action. You will be required to update the version and add release notes.
8+
The version string should have the form `1.0.0-beta.x` for beta releases, there should not be a `v` prefix on the tag name.
89
* If the release notes are complicated and don't fit on a single line it is easier to rather update those after the release is completed by updating the release notes in the new release.

0 commit comments

Comments
 (0)