Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deserialize timestamps as Instant #605

Merged
merged 21 commits into from
May 5, 2022
Merged

Deserialize timestamps as Instant #605

merged 21 commits into from
May 5, 2022

Conversation

lukellmann
Copy link
Member

Like #586 but for Instant:

  • serialize timestamps with the default InstantIso8601Serializer or custom InstantInEpochMillisecondsSerializer/InstantInEpochSecondsSerializer
  • change types to Instant where applicable

Because of Kotlin/kotlinx.serialization#1895, using typealiases like those for Duration is not possible yet.

lukellmann added 21 commits April 28, 2022 05:14
@lukellmann
Instant serializers
fe5cc57
@lukellmann
use Instant for UpdateStatus.since
09eab0d
@lukellmann
use Instant for Activity timestamps
113d492
@lukellmann
use Instant for Typing Start timestamps
a4dc677
@lukellmann
use Instant for request_to_speak_timestamp
75a7e23
@lukellmann
use Instant for DiscordTemplate
4b2cda9
@lukellmann
use Instant for last_pin_timestamp
3656ac7
@lukellmann
use Instant for Message timestamps
d874a8c
@lukellmann
use Instant for archive_timestamp
f76e358
@lukellmann
use Instant for join_timestamp
5ac33df
@lukellmann
use Instant for Embed.timestamp
dfa6873
@lukellmann
use Instant for joined_at
b9f5def
@lukellmann
use Instant for premium_since
2427cd5
@lukellmann
use Instant for synced_at
64d8824
@lukellmann
use Instant for DiscordCreatedInvite.createdAt
68ffd74
@lukellmann
fix tests
096fe19
@lukellmann
typealiases
ec07c32
@lukellmann
more and simpler tests
29b3708
@lukellmann
throw SerializationException on overflow in InstantInEpochMillisecond…
74d1bf4 
…sSerializer
@lukellmann
Range check to prevent false positive
a7c0ad3
@lukellmann
Don't use typealiases because of Kotlin/kotlinx.serialization#1895
b5fb350
@HopeBaron HopeBaron merged commit 1875717 into kordlib:0.8.x May 5, 2022
@lukellmann lukellmann deleted the changes/serialize-instants branch May 5, 2022 18:47
lukellmann added a commit that referenced this pull request Feb 10, 2023
@lukellmann
Update Kotlin to 1.8.20-Beta
afa26ff 
Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20-Beta, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20-Beta. However,
they are unlikely to affect anyone since only generated symbols that
aren't supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Feb 17, 2023
@lukellmann
Update Kotlin to 1.8.20-Beta
ef98feb 
Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20-Beta, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20-Beta. However,
they are unlikely to affect anyone since only generated symbols that
aren't supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Feb 17, 2023
@lukellmann
Update Kotlin to 1.8.20-Beta
13950a0 
Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20-Beta, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20-Beta. However,
they are unlikely to affect anyone since only generated symbols that
aren't supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Mar 8, 2023
@lukellmann
Update Kotlin to 1.8.20-RC
0ad7565 
Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20-RC, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20-RC. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Mar 9, 2023
@lukellmann
Update Kotlin to 1.8.20-RC
30c68a0 
Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20-RC, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20-RC. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Mar 9, 2023
@lukellmann
Update dependencies
bd4c557 
* Kotlin 1.8.10 -> 1.8.20-RC
* KSP 1.8.10-1.0.9 -> 1.8.20-RC-1.0.9
* kotlinx.coroutines 1.6.4 -> 1.7.0-Beta

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20-RC, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20-RC. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Mar 21, 2023
@lukellmann
Update dependencies
d5eba20 
* Kotlin 1.8.10 -> 1.8.20-RC
* KSP 1.8.10-1.0.9 -> 1.8.20-RC-1.0.9
* kotlinx.coroutines 1.6.4 -> 1.7.0-Beta

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20-RC, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20-RC. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Mar 25, 2023
@lukellmann
Update dependencies
1972270 
* Kotlin 1.8.10 -> 1.8.20-RC2
* KSP 1.8.10-1.0.9 -> 1.8.20-RC2-1.0.9
* kotlinx.coroutines 1.6.4 -> 1.7.0-Beta
* AtomicFU 0.20.0 -> 0.20.1

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20-RC2, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20-RC2. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Apr 2, 2023
@lukellmann
Update dependencies
eeeb27f 
* Kotlin 1.8.10 -> 1.8.20
* KSP 1.8.10-1.0.9 -> 1.8.20-RC2-1.0.9
* kotlinx.coroutines 1.6.4 -> 1.7.0-Beta
* AtomicFU 0.20.0 -> 0.20.1

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Apr 3, 2023
@lukellmann
Update dependencies
0a1e7ce 
* Kotlin 1.8.10 -> 1.8.20
* KSP 1.8.10-1.0.9 -> 1.8.20-1.0.10
* kotlinx.coroutines 1.6.4 -> 1.7.0-Beta
* AtomicFU 0.20.0 -> 0.20.1

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Apr 5, 2023
@lukellmann
Update dependencies
87bd1b7 
* Kotlin 1.8.10 -> 1.8.20
* KSP 1.8.10-1.0.9 -> 1.8.20-1.0.10
* kotlinx.coroutines 1.6.4 -> 1.7.0-Beta
* AtomicFU 0.20.0 -> 0.20.1

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Apr 6, 2023
@lukellmann
Update dependencies
e065023 
* Kotlin 1.8.10 -> 1.8.20
* KSP 1.8.10-1.0.9 -> 1.8.20-1.0.10
* kotlinx.coroutines 1.6.4 -> 1.7.0-Beta
* AtomicFU 0.20.0 -> 0.20.2
* KotlinPoet 1.12.0 -> 1.13.0

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Apr 14, 2023
@lukellmann
Update dependencies
ccddcd6 
* Kotlin 1.8.10 -> 1.8.20
* KSP 1.8.10-1.0.9 -> 1.8.20-1.0.10
* kotlinx.coroutines 1.6.4 -> 1.7.0-Beta
* AtomicFU 0.20.0 -> 0.20.2
* KotlinPoet 1.12.0 -> 1.13.0

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Apr 15, 2023
@lukellmann
Update dependencies
b7b0639 
* Kotlin 1.8.10 -> 1.8.20
* KSP 1.8.10-1.0.9 -> 1.8.20-1.0.10
* kotlinx.coroutines 1.6.4 -> 1.7.0-Beta
* AtomicFU 0.20.0 -> 0.20.2
* KotlinPoet 1.12.0 -> 1.13.0

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Apr 19, 2023
@lukellmann
Update dependencies
5c865e8 
* Kotlin 1.8.10 -> 1.8.20
* KSP 1.8.10-1.0.9 -> 1.8.20-1.0.11
* kotlinx.coroutines 1.6.4 -> 1.7.0-RC
* AtomicFU 0.20.0 -> 0.20.2
* Binary compatibility validator 0.13.0 -> 0.13.1
* KotlinPoet 1.12.0 -> 1.13.0
* MockK 1.13.4 -> 1.13.5

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Apr 19, 2023
@lukellmann
Update dependencies
44332ff 
* Kotlin 1.8.10 -> 1.8.20
* KSP 1.8.10-1.0.9 -> 1.8.20-1.0.11
* Ktor 2.2.4 -> 2.3.0
* kotlinx.coroutines 1.6.4 -> 1.7.0-RC
* AtomicFU 0.20.0 -> 0.20.2
* Binary compatibility validator 0.13.0 -> 0.13.1
* KotlinPoet 1.12.0 -> 1.13.0
* MockK 1.13.4 -> 1.13.5

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.20, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.20. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Apr 25, 2023
@lukellmann
Update dependencies
ae32d06 
* Kotlin 1.8.10 -> 1.8.21
* Ktor 2.2.4 -> 2.3.0
* kotlinx.coroutines 1.6.4 -> 1.7.0-RC
* kotlin-node 18.14.0-pre.502 -> 18.16.0-pre.543
* KSP 1.8.10-1.0.9 -> 1.8.20-1.0.11
* KotlinPoet 1.12.0 -> 1.13.0
* MockK 1.13.4 -> 1.13.5
* AtomicFU 0.20.0 -> 0.20.2
* Binary compatibility validator 0.13.0 -> 0.13.1
* gradle-buildconfig-plugin 3.1.0 -> 4.0.2

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.21, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.21. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Apr 27, 2023
@lukellmann
Update dependencies
60c9c0e 
* Kotlin 1.8.10 -> 1.8.21
* Ktor 2.2.4 -> 2.3.0
* kotlinx.coroutines 1.6.4 -> 1.7.0-RC
* kotlin-node 18.14.0-pre.502 -> 18.16.0-pre.543
* KSP 1.8.10-1.0.9 -> 1.8.21-1.0.11
* KotlinPoet 1.12.0 -> 1.13.0
* JUnit 5 5.9.2 -> 5.9.3
* MockK 1.13.4 -> 1.13.5
* AtomicFU 0.20.0 -> 0.20.2
* Binary compatibility validator 0.13.0 -> 0.13.1
* gradle-buildconfig-plugin 3.1.0 -> 4.0.2

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.21, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.21. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Apr 29, 2023
@lukellmann
Update dependencies
692a07c 
* Kotlin 1.8.10 -> 1.8.21
* Ktor 2.2.4 -> 2.3.0
* kotlinx.coroutines 1.6.4 -> 1.7.0-RC
* kotlin-node 18.14.0-pre.502 -> 18.16.0-pre.543
* KSP 1.8.10-1.0.9 -> 1.8.21-1.0.11
* KotlinPoet 1.12.0 -> 1.13.1
* JUnit 5 5.9.2 -> 5.9.3
* MockK 1.13.4 -> 1.13.5
* AtomicFU 0.20.0 -> 0.20.2
* Binary compatibility validator 0.13.0 -> 0.13.1
* gradle-buildconfig-plugin 3.1.0 -> 4.0.2

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.21, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.21. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request Apr 29, 2023
@lukellmann
Update dependencies
12c8308 
* Kotlin 1.8.10 -> 1.8.21
* Ktor 2.2.4 -> 2.3.0
* kotlinx.coroutines 1.6.4 -> 1.7.0-RC
* kotlin-node 18.14.0-pre.502 -> 18.16.0-pre.543
* KSP 1.8.10-1.0.9 -> 1.8.21-1.0.11
* KotlinPoet 1.12.0 -> 1.13.1
* JUnit 5 5.9.2 -> 5.9.3
* MockK 1.13.4 -> 1.13.5
* AtomicFU 0.20.0 -> 0.20.2
* Binary compatibility validator 0.13.0 -> 0.13.1
* gradle-buildconfig-plugin 3.1.0 -> 4.0.2

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.21, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.21. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request May 2, 2023
@lukellmann
Update dependencies
a62fc9a 
* Kotlin 1.8.10 -> 1.8.21
* Ktor 2.2.4 -> 2.3.0
* kotlinx.coroutines 1.6.4 -> 1.7.0-RC
* kotlin-node 18.14.0-pre.502 -> 18.16.3-pre.546
* KSP 1.8.10-1.0.9 -> 1.8.21-1.0.11
* KotlinPoet 1.12.0 -> 1.13.1
* JUnit 5 5.9.2 -> 5.9.3
* MockK 1.13.4 -> 1.13.5
* AtomicFU 0.20.0 -> 0.20.2
* Binary compatibility validator 0.13.0 -> 0.13.1
* gradle-buildconfig-plugin 3.1.0 -> 4.0.4

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.21, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.21. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request May 5, 2023
@lukellmann
Update dependencies
5f07339 
* Kotlin 1.8.10 -> 1.8.21
* Ktor 2.2.4 -> 2.3.0
* kotlinx.coroutines 1.6.4 -> 1.7.0
* kotlin-node 18.14.0-pre.502 -> 18.16.3-pre.546
* KSP 1.8.10-1.0.9 -> 1.8.21-1.0.11
* KotlinPoet 1.12.0 -> 1.13.2
* JUnit 5 5.9.2 -> 5.9.3
* MockK 1.13.4 -> 1.13.5
* AtomicFU 0.20.0 -> 0.20.2
* Binary compatibility validator 0.13.0 -> 0.13.1
* gradle-buildconfig-plugin 3.1.0 -> 4.0.4

Warnings about duplicate library name with AtomicFU are no longer
present with kotlinx.coroutines 1.7.0 and AtomicFU 0.20.2, so -Werror
can be turned on again.

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.21, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.21. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
@lukellmann lukellmann mentioned this pull request May 5, 2023
Merged
lukellmann added a commit that referenced this pull request May 13, 2023
@lukellmann
Update dependencies
a768aca 
* Kotlin 1.8.10 -> 1.8.21
* Ktor 2.2.4 -> 2.3.0
* kotlinx.coroutines 1.6.4 -> 1.7.1
* kotlinx.serialization 1.5.0 -> 1.5.1
* kotlin-node 18.14.0-pre.502 -> 18.16.3-pre.546
* KSP 1.8.10-1.0.9 -> 1.8.21-1.0.11
* KotlinPoet 1.12.0 -> 1.13.2
* JUnit 5 5.9.2 -> 5.9.3
* MockK 1.13.4 -> 1.13.5
* AtomicFU 0.20.0 -> 0.20.2
* Binary compatibility validator 0.13.0 -> 0.13.1
* gradle-buildconfig-plugin 3.1.0 -> 4.0.4

Warnings about duplicate library name with AtomicFU are no longer
present with kotlinx.coroutines 1.7.0 and AtomicFU 0.20.2, so -Werror
can be turned on again.

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.21, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.21. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request May 21, 2023
@lukellmann
Update dependencies
7126e59 
* Kotlin 1.8.10 -> 1.8.21
* Ktor 2.2.4 -> 2.3.0
* kotlinx.coroutines 1.6.4 -> 1.7.1
* kotlinx.serialization 1.5.0 -> 1.5.1
* kotlin-node 18.14.0-pre.502 -> 18.16.3-pre.546
* KSP 1.8.10-1.0.9 -> 1.8.21-1.0.11
* KotlinPoet 1.12.0 -> 1.13.2
* JUnit 5 5.9.2 -> 5.9.3
* MockK 1.13.4 -> 1.13.5
* AtomicFU 0.20.0 -> 0.20.2
* Binary compatibility validator 0.13.0 -> 0.13.1
* gradle-buildconfig-plugin 3.1.0 -> 4.0.4

Warnings about duplicate library name with AtomicFU are no longer
present with kotlinx.coroutines 1.7.1 and AtomicFU 0.20.2, so -Werror
can be turned on again.

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.21, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.21. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
lukellmann added a commit that referenced this pull request May 21, 2023
@lukellmann
Update dependencies (#826)
eaf0b35 
* Kotlin 1.8.10 -> 1.8.21
* Ktor 2.2.4 -> 2.3.0
* kotlinx.coroutines 1.6.4 -> 1.7.1
* kotlinx.serialization 1.5.0 -> 1.5.1
* kotlin-node 18.14.0-pre.502 -> 18.16.3-pre.546
* KSP 1.8.10-1.0.9 -> 1.8.21-1.0.11
* KotlinPoet 1.12.0 -> 1.13.2
* JUnit 5 5.9.2 -> 5.9.3
* MockK 1.13.4 -> 1.13.5
* AtomicFU 0.20.0 -> 0.20.2
* Binary compatibility validator 0.13.0 -> 0.13.1
* gradle-buildconfig-plugin 3.1.0 -> 4.0.4

Warnings about duplicate library name with AtomicFU are no longer
present with kotlinx.coroutines 1.7.1 and AtomicFU 0.20.2, so -Werror
can be turned on again.

Using typealiases for overriding the default Instant serializer wasn't
possible in #605 because of
Kotlin/kotlinx.serialization#1895.
Since this Bug was fixed in Kotlin 1.8.21, the typealiases
dev.kord.common.serialization.InstantInEpochMilliseconds and
dev.kord.common.serialization.InstantInEpochSeconds can now be used.

The changes in the public API are probably because of changes in the
serialization and AtomicFU plugins with Kotlin 1.8.21. However, they
are unlikely to affect anyone since only generated symbols that aren't
supposed to be accessed directly were touched.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@lukellmann @HopeBaron