ares_api

[sleek ember]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1378979041691828365

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[tulip finch]

No, define in code will overwirte and take precedences over the default API version in Dashboard

[iron tulip]

just to confirm this will enforce the same api version on dashboard apiVersion: '2025-04-30.basil',

Am i right?

[tulip finch]

Which version is in your Dashboard currently?

It does enforce the API version to the API you are calling, but it doesn't make any change to your Dashboard

[iron tulip]

we are using 2020-08-27 currently, pretty behind

I am merging a code change with all the updates required in basil api version listed above.

[tulip finch]

Yes so you would want to keep setting the 2025 API version in your code, and test it through, before finally update your API version in Dashboard

[iron tulip]

the issue is I don't see the api version apiVersion: '2025-04-30.basil', on dashboard anymore and that is why i was confirming if I need to make both the changes or if the code change is sufficient.

[tulip finch]

Um yes that's normal. You only see the latest version there as the Upgrade option

[iron tulip]

so what should I do in this situation where my code has apiVersion: '2025-04-30.basil' but it is not available on dashboard? If i merge the change as it is, does it have any impact?

[tulip finch]

No, your code will continue calling 2025-04-30.basil