Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

API Versioning

Open
#4 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
api, documentation

Research direction

Start by reviewing the versioning section of the API guidelines and compare its recommendations with the release practices described here. Check the two existing comments for context, then seek agreement on whether the guidance should change; done means the project has an accepted, updated position on API versioning.

Written by the indexing model from the issue text.

Description

feedback

Let me first off say, thank you for doing this collaboratively and for all the work that has gone into this.

I do find the versioning section to be very prescriptive. Versioning is hard. Our project currently releases every day and usually has API changes on every release. Not breaking changes, but usually small additions. We're starting to get third-party consumers and will version when we introduce a breaking change.

I feel versioning at this fidelity forces an event driven architecture which is an unneeded complexity for many applications.

Feel free to hit me up in the lab if you'd like to discuss more.

Dominant language
No language data
Stars
34
Forks
10
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bcgov/api-guidelines

All issues in bcgov/api-guidelines

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.