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

section in API Guide for changes in behavior and backward incompatibilities #10060

Closed
pdurbin opened this issue Oct 27, 2023 · 0 comments · Fixed by #10127
Closed

section in API Guide for changes in behavior and backward incompatibilities #10060

pdurbin opened this issue Oct 27, 2023 · 0 comments · Fixed by #10127
Labels
Feature: API Guide Type: Suggestion an idea User Role: API User Makes use of APIs
Milestone
6.1

Comments

@pdurbin
Copy link
Member

pdurbin commented Oct 27, 2023

We try very hard to keep our APIs backward compatible.

However, breaking changes do happen and we currently only mention them in release notes. We should keep doing this but there should also be a centralized list, some sort of changelog, probably in the API Guide.
@pdurbin pdurbin changed the title section to API Guide for changes in behavior and backward incompatibilities section in API Guide for changes in behavior and backward incompatibilities Oct 30, 2023
This was referenced Oct 30, 2023
Closed
Merged
@pdurbin pdurbin mentioned this issue Nov 17, 2023
Merged
pdurbin added a commit to jp-tosca/dataverse that referenced this issue Nov 17, 2023
@pdurbin
fix bullet IQSS#10060 IQSS#10070
2433114
pdurbin added a commit to jp-tosca/dataverse that referenced this issue Nov 17, 2023
@pdurbin
add release note for API changelog IQSS#10060
640f69e
@pdurbin pdurbin added this to the 6.1 milestone Nov 17, 2023
pdurbin added a commit that referenced this issue Nov 28, 2023
@pdurbin
add "v" to make anchor links meaningful #9464 #10060
d8e327d 
Anchors like #v6.1 are much better than #id1, which is meaningless.
@pdurbin pdurbin mentioned this issue Dec 1, 2023
Closed
@poikilotherm poikilotherm mentioned this issue Mar 11, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature: API Guide Type: Suggestion an idea User Role: API User Makes use of APIs
Projects
None yet
Milestone
6.1
Development

Successfully merging a pull request may close this issue.

Add condition for 401 on invalid key and changelog on API Guide jp-tosca/dataverse
1 participant
@pdurbin