docs: Add release notes

[mikemckiernan]

Description

Add release notes so that recent additions to this large set of HTML pages are more findable.

Related Issue(s)

Checklist

• I've read the CONTRIBUTING guidelines.
• I've updated the documentation if applicable.
• I've added tests if applicable.
• @mentions of the person or team responsible for reviewing proposed changes.

[github-actions]

Documentation preview

https://nvidia.github.io/NeMo-Guardrails/review/pr-1141

[cparisien]

Thanks Mike. This should also link to the github CHANGELOG.md that sits at the top level of the repo. And @Pouyanpi, @tgasser-nv, when we update that changelog on a release we should link to this release-notes.md.

[Pouyanpi]

Mike please correct me if I'm wrong but I think this was never supported. I'll try to reproduce it using v0.13.0 and let you know.

[Pouyanpi]

@mikemckiernan It was not supported but we could call it a bug

git checkout v0.13.0

then

from nemoguardrails import RailsConfig, LLMRails

config = RailsConfig.from_path("./examples/configs/gs_content_safety/config")
rails = LLMRails(config, verbose=False)


# it is not set in config
assert config.models[0].model is None
assert not hasattr(config.models[0], "model_name")

rails = LLMRails(config, verbose=False)
# meta/llma-3.3-70b-instruct is define in the config with model_name
# but it is not used as main llm
assert rails.llm.model != "meta/llama-3.3-70b-instruct"

# actually, it is using the default provided by ChatNVIDIA()
assert rails.llm.model == "meta/llama3-8b-instruct"

# it works because it is using the default provided by ChatNVIDIA
rails.generate(messages=[{"role": "user", "content": "what can you do?"}])

[mikemckiernan]

@mikemckiernan It was not supported but we could call it a bug

Thanks for the help with this Pouyan. I can't wait for Tim to get started on refactoring some config work. This is not the kind of surprise that I like.

I moved the changes to the GS pages to PR #1146 to keep the changes a little more manageable.