Release 0.1.3#26
Conversation
- Bump version 0.1.2 -> 0.1.3 (Project.toml, README status, USER_AGENT). - CHANGELOG: cut the [0.1.3] - 2026-06-04 section from [Unreleased] (HTTP retries, backpressured foreach_record, start_dt/end_dt rename) and repair the footer compare links (the [Unreleased] link still pointed at v0.1.1 and the [0.1.2] entry was missing). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e810e4a737
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| name = "DatabentoAPI" | ||
| uuid = "feb0aed8-3291-460b-9688-521dcb17a4bf" | ||
| version = "0.1.2" | ||
| version = "0.1.3" |
There was a problem hiding this comment.
Bump the breaking release out of the patch series
This release documents a breaking rename from start / end_ to start_dt / end_dt in the new 0.1.3 changelog section, so publishing it as patch version 0.1.3 lets existing Julia users with compat such as "0.1" or ^0.1.2 resolve to a version where their current calls fail. Since the package states it follows SemVer, this should be a new compatible-series version (for example 0.2.0, with the README/user-agent/changelog links aligned) or the breaking API change should not ship in this patch release.
Useful? React with 👍 / 👎.
|
Superseded by #27 — this should be 0.2.0 (breaking change → minor bump under SemVer), not 0.1.3. |
Version bump to 0.1.3.
Changes since 0.1.2 (already on
mainvia #25)max_retriesknob).start/end_→start_dt/end_dt.foreach_recordnow applies real backpressure with deterministic teardown.This PR
Project.tomlversion0.1.2→0.1.30.1.3USER_AGENT→DatabentoAPI.jl/0.1.3CHANGELOG.md: cut the[0.1.3] - 2026-06-04section from[Unreleased], and repaired the footer compare links (the[Unreleased]link still pointed atv0.1.1and the[0.1.2]entry was missing).After merge, register with
@JuliaRegistrator registeron the merge commit; TagBot then tagsv0.1.3and creates the GitHub release.🤖 Generated with Claude Code