-
Notifications
You must be signed in to change notification settings - Fork 14
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
chore: release main #393
chore: release main #393
Conversation
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 need #395 first
cec3ac5
to
a222246
Compare
a222246
to
33c9b01
Compare
All services require the |
33c9b01
to
b3add60
Compare
ff49bfa
to
3a574b1
Compare
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.
update db-service version in all other packages before merging.
2ffeb2f
to
3ceaece
Compare
0ad0fb7
to
927c58e
Compare
927c58e
to
733c8f8
Compare
3678262
to
e9836ec
Compare
@BobdenOs @patricebender from my point of view we are ready to go. For some reason release-please removed my commits for increasing db-service version and cds peer version: .Could you please double check how we can include those :) |
![]() Looks strange, did you directly pushed this change to this branch? Maybe increase the versions in a PR instead? |
... ok, we can't bump db-service version as 1.6 isn't released yet 😅 how do you normally handle this? |
in a perfect world we would separately release the db-service and then bump the versions in the other packages. I would propose that we force merge #437 and immediately release our services after. Edit: oh, i guess then the release pipeline would fail :( I will check if there is a mechanism in release please to release the |
we can't do that in two separate prs? |
I think I can release the db-service separately, via CLI, never done it before but I will try |
What I read from the I guess force merging #437 should work, right ? |
I guess the release pipeline would then fail :( |
e9836ec
to
d1584c6
Compare
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.
🚀
🤖 Release is at https://github.com/cap-js/cds-dbs/releases/tag/sqlite-v1.5.0 🌻 |
🤖 Release is at https://github.com/cap-js/cds-dbs/releases/tag/postgres-v1.5.0 🌻 |
🤖 Release is at https://github.com/cap-js/cds-dbs/releases/tag/hana-v0.0.4 🌻 |
🤖 I have created a release beep boop
db-service: 1.6.0
1.6.0 (2024-02-02)
Added
INSERT
,UPDATE
andUPSERT
(#384) (4644483)Fixed
cqn4sql
: only transform list if necessary (#438) (8a7ec65)list
infrom.where
(#429) (3288e94)sqlite: 1.5.0
1.5.0 (2024-02-02)
Added
Fixed
postgres: 1.5.0
1.5.0 (2024-02-02)
Added
Fixed
hana: 0.0.4
0.0.4 (2024-02-02)
Added
Fixed
!=
and==
implementation for @cap-js/hana (#426) (9b7b5a0)This PR was generated with Release Please. See documentation.