-
Notifications
You must be signed in to change notification settings - Fork 53
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
Migration Plans for 2023-10 breaking changes? #115
Comments
Was about to create an issue for that. According to this page, they will end the support for the 2023-07 version on 15/01/2024, which is basically 3 months from now. And looks like this repo does not use the Since the last update this repo had was 9 months ago, and we have a more updated fork probably we should fork the already forked repo and add support to the new version. |
Agree @willnaoosmith ! I'd also be open to creating a PR into this repo with fixes to the breaking changes but not sure if this repo is actively managed anymore? |
@shanaxel42 the current repository we are talking does not look like it's actively maintained. |
Hi there! I'm doing some changes on the fork I mentioned before, here's my fork. monday = MondayClient(
token = "YourTokenHere",
headers = {'API-Version' : '2023-10'}
) While changing the requests to match the I opened a discussion on the Monday forum about it. [Edit] |
By the way, I think I made it! There's not that much stuff that this module uses that changes with the What changes:
monday = MondayClient(
token = "YourTokenHere",
headers = {'API-Version' : '2023-10'}
)
monday.updates.fetch_updates_for_item(item_id="ItemIDHere", limit="LimitHere")
monday.items.fetch_items_by_column_value(board_id='BoardIDHere', column_id="ColumnIDHere", value="ColumnValueHere") If anyone wants to try it, just install it using |
Hi all! Wondering if there is a plan to refactor this client to support the new 2023-10 api version with breaking changes?
Thanks!
https://developer.monday.com/api-reference/docs/migrating-to-v-2023-10
The text was updated successfully, but these errors were encountered: