Reintegrate 0.14.0 release metadata into main

[programmersd21]

Recovery PR: the original #12 is marked merged, but the current main tree still lacks the v0.14.0 release entry and release metadata. This branch is older than main, so review the exact diff and run CI before merging; do not tag or publish a release as part of this PR.

Summary by Sourcery

Reintegrate the v0.14.0 release metadata and version alignment into the main branch without publishing release artifacts.

Enhancements:

• Restore the v0.14.0 release metadata, compatibility notes, and package-management documentation in the changelog.
• Align runtime version reporting, HTTP identification, and Rust crate metadata with the 0.14.0 release while preserving the independent native ABI version.

Documentation:

• Document the v0.14.0 package import, manifest entry-point, installation reliability, and release compatibility changes.

Chores:

• Keep the standalone and Rust-embedded C runtime metadata consistent.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 73e021ce-20a7-44d5-bda2-8116ac05488e

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}

[sourcery-ai]

Reviewer's Guide

Reintegrates the v0.14.0 release entry and updates Rust metadata, runtime version reporting, HTTP identification, and embedded/standalone C sources to match the release while preserving ABI version 1; review the exact older-branch diff and run CI, but do not tag or publish a release.

File-Level Changes

Change	Details	Files
Restore the v0.14.0 release documentation and explicitly preserve release-gating constraints.	Document package layouts, manifest entry points, installation/cache reliability, compatibility, and release-readiness requirements. State that tagging or publishing v0.14.0 is outside this PR and depends on follow-up PRs and final checks.	RELEASES.md
Align Rust package metadata and documentation with the 0.14.0 language release while keeping the native ABI independently versioned.	Bump flintlang and flintlang-sys package versions and their dependency/example lockfile references. Update crate installation examples and version/ABI documentation.	rust/Cargo.lock rust/examples/rust-native/Cargo.lock rust/examples/tui-native/Cargo.lock rust/flintlang-sys/Cargo.toml rust/flintlang-sys/README.md rust/flintlang/Cargo.toml rust/flintlang/README.md
Synchronize release-facing runtime behavior and HTTP identification across standalone and Rust-embedded builds.	Report 0.14.0 for language, runtime, package format, bytecode, and lockfile versions while retaining native ABI version 1. Change the default HTTP User-Agent to flint/0.14.0. Keep equivalent embedded and standalone C runtime changes, with package help formatting updates in the embedded source.	src/main.c src/runtime/http.c rust/flintlang/c-src/src/runtime/http.c rust/flintlang/c-src/src/pkg.c

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="src/runtime/http.c" line_range="522" />
<code_context>
 	}
 	if (!has_ua) {
-		buf_append(&req, "User-Agent: flint/0.7.0\r\n", 25);
+		buf_append(&req, "User-Agent: flint/0.14.0\r\n", strlen("User-Agent: flint/0.14.0\r\n"));
 	}
 	if (!has_accept) {
</code_context>
<issue_to_address>
**HTTPS requests use curl identity**

When an HTTPS request does not provide its own User-Agent, `curl_fetch` forwards only caller-provided headers to curl and never adds the new default, so HTTPS requests use curl’s default User-Agent instead of identifying Flint to the server.

Add the Flint default User-Agent to `curl_fetch` when the caller has not supplied one, and keep the embedded copy in sync.

Also at `rust/flintlang/c-src/src/runtime/http.c:522`.
</issue_to_address>

Sourcery assessment

Approval pending. 1 finding to address first.

Blocking findings: src/runtime/http.c:522

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[sourcery-ai]

🟡 Medium · HTTPS requests use curl identity

When an HTTPS request does not provide its own User-Agent, curl_fetch forwards only caller-provided headers to curl and never adds the new default, so HTTPS requests use curl’s default User-Agent instead of identifying Flint to the server.

Add the Flint default User-Agent to curl_fetch when the caller has not supplied one, and keep the embedded copy in sync.

Also at rust/flintlang/c-src/src/runtime/http.c:522.

Prompt for AI agents

In `src/runtime/http.c` at line 522:

**HTTPS requests use curl identity**

When an HTTPS request does not provide its own User-Agent, `curl_fetch` forwards only caller-provided headers to curl and never adds the new default, so HTTPS requests use curl’s default User-Agent instead of identifying Flint to the server.

Add the Flint default User-Agent to `curl_fetch` when the caller has not supplied one, and keep the embedded copy in sync.

Also at `rust/flintlang/c-src/src/runtime/http.c:522`.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook