Please don't break semantic versioning (& better changelogs/releases?)

[ldorigo]

Checked other resources

• I added a very descriptive title to this issue.
• I searched the LangChain documentation with the integrated search.
• I used the GitHub search to find a similar question and didn't find it.
• I am sure that this is a bug in LangChain rather than my code.

Example Code

In a recent langgraph version, do

        graph.add_conditional_edges(
            start_key="foo",
            condition=select_next_node,
            conditional_edge_mapping={
                'foo': 'bar'
            },
        )

This will break, since the parameter names changed.

Error Message and Stack Trace (if applicable)

No response

Description

Hello, due to a combination of

1. Not using releases
2. Using very nondescript commit messages
   
3. Not following semantic versioning (i.e. introducing breaking changes in minor versions)

This library introduces quite a maintenance burden and is hard to keep track of.

System Info

System Information

OS: Linux
OS Version: #1 SMP PREEMPT_DYNAMIC Fri, 17 May 2024 11:49:30 +0000
Python Version: 3.12.3 (main, Apr 23 2024, 09:16:07) [GCC 13.2.1 20240417]

Package Information

langchain_core: 0.1.52
langchain: 0.1.20
langchain_community: 0.0.38
langsmith: 0.1.63
langchain_cohere: 0.1.4
langchain_mongodb: 0.1.5
langchain_openai: 0.1.6
langchain_text_splitters: 0.0.2
langchainhub: 0.1.16
langgraph: 0.0.30

Packages not installed (Not Necessarily a Problem)

The following packages were not found:

langserve

[hinthornw]

Thanks for the feedback, and for your patience with the breaks we've made thus far - definitely agree with this being a problem. Over the next month we're seeking to mature our release process and move towards proper versioning

[hinthornw]

Converted this to a discussion - feel free to add more feedback here! Open to converting back if needed

[nfcampos]

We've added release notes, and adopted semantic versioning starting with release 0.1.0