chore(docs): mark pact-net 5.x as stable #525
Conversation
|
Oh I totally forgot to do that, thanks! I think 4.x would only receive updates now for a major issue or big security problem. The breaking changes in 5.x are pretty easy to migrate, and it's complicated if the 4.x fix needed an FFI update. So that's probably a kind of LTS? Unless you can think of a better term. Problem with LTS is we have no defined period of support. Maybe 'maintenance'? I'm struggling to think of a good term. |
|
I think marking as deprecated will just prompt those to migrate to v5. You’ve created upgrade guides and I’ve updated the workshops and added the contents from the docs folder to the website in this pr, so think we are in a good position also posted in todays blog https://docs.pact.io/blog/2024/10/28/pact-open-source-update-oct-2024#pact-net |
|
Yeah fine by me. Do you want to update the PR with that change at the same time then? |
Users are advised to migrate to pact-net 5.x https://github.com/pact-foundation/pact-net/blob/master/docs/upgrading-to-5.md
done now 👍🏾 |
Should 4.x be marked as deprecated, or is that still supported for a certain period of time, to allow for migration to 4.x and potentially allow for changes/fixes to be released to the 4.x line?