-
Notifications
You must be signed in to change notification settings - Fork 532
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.
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
Update deps (minor) on server release group in the client release group #16358
Update deps (minor) on server release group in the client release group #16358
Conversation
Updated the following: client (release group) Dependencies on server updated: @fluidframework/gitresources: 1.0.0-173913 @fluidframework/server-kafka-orderer: 1.0.0-173913 @fluidframework/server-lambdas: 1.0.0-173913 @fluidframework/server-lambdas-driver: 1.0.0-173913 @fluidframework/server-local-server: 1.0.0-173913 @fluidframework/server-memory-orderer: 1.0.0-173913 @fluidframework/protocol-base: 1.0.0-173913 @fluidframework/server-routerlicious: 1.0.0-173913 @fluidframework/server-routerlicious-base: 1.0.0-173913 @fluidframework/server-services: 1.0.0-173913 @fluidframework/server-services-client: 1.0.0-173913 @fluidframework/server-services-core: 1.0.0-173913 @fluidframework/server-services-ordering-kafkanode: 1.0.0-173913 @fluidframework/server-services-ordering-rdkafka: 1.0.0-173913 @fluidframework/server-services-ordering-zookeeper: 1.0.0-173913 @fluidframework/server-services-shared: 1.0.0-173913 @fluidframework/server-services-telemetry: 1.0.0-173913 @fluidframework/server-services-utils: 1.0.0-173913 @fluidframework/server-test-utils: 1.0.0-173913
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We just need to rename the buildhierarchy calls or we will have build problems, I think
⯆ @fluid-example/bundle-size-tests: -26 Bytes
Baseline commit: b2e79b4 |
@NicholasCouri I'm still not sure we should merge this, since it requires us changing client code to use the wrong name. We can merge this, but it's not required. We could instead prerelease another build and integrate that build, with the correct API name. Or go straight to releasing 1.0. Your call. I don't mind doing these extra steps for the experience, I just want to be clear what's necessary vs not. I won't be online much tomorrow, so ping the release engineers if anything can't wait until Friday. |
I'm ok either way. I can publish a new prerelease. |
@NicholasCouri I'm merging since the tests pass; I think we will need to update tinylicious before we release 6.0, but we can do that in separate commits. |
Related PR bumping tinylicious: #16380 |
Updated the following:
client (release group)
Dependencies on server updated:
@fluidframework/gitresources: 1.0.0-1.0.0-175213
@fluidframework/server-kafka-orderer: 1.0.0-175213
@fluidframework/server-lambdas: 1.0.0-175213
@fluidframework/server-lambdas-driver: 1.0.0-175213
@fluidframework/server-local-server: 1.0.0-175213
@fluidframework/server-memory-orderer: 1.0.0-175213
@fluidframework/protocol-base: 1.0.0-175213
@fluidframework/server-routerlicious: 1.0.0-175213
@fluidframework/server-routerlicious-base: 1.0.0-175213
@fluidframework/server-services: 1.0.0-175213
@fluidframework/server-services-client: 1.0.0-175213
@fluidframework/server-services-core: 1.0.0-175213
@fluidframework/server-services-ordering-kafkanode: 1.0.0-175213
@fluidframework/server-services-ordering-rdkafka: 1.0.0-175213
@fluidframework/server-services-ordering-zookeeper: 1.0.0-175213
@fluidframework/server-services-shared: 1.0.0-175213
@fluidframework/server-services-telemetry: 1.0.0-175213
@fluidframework/server-services-utils: 1.0.0-175213
@fluidframework/server-test-utils: 1.0.0-175213