Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Bump to v1.0 (stable semver release)

未关闭
#1,801 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
release

调研方向

Start by reviewing the repository's current 0.x release and versioning setup, then assess the proposed breaking-change and deprecation questions, including no_extract and old auth patterns. Done means the 1.0 scope and semver policy are agreed, including whether a deprecation pass is required first.

由索引模型根据 Issue 内容生成。

描述

TSC has been versioned as 0.x since its initial release, despite being a widely-used, production-grade library. Staying at 0.x implies instability and allows semver-breaking changes without a major version bump, which is confusing for users who depend on it.

Proposal: release the next version as 1.0, signalling stability and committing to semver conventions going forward. This means:

  • Breaking changes require a major version bump (2.0, etc.)
  • Non-breaking additions use minor bumps (1.1, 1.2, ...)
  • Bug fixes use patch bumps (1.0.1, ...)

This aligns with the approach used by other Tableau SDKs (e.g. the Migrations SDK).

Open questions:

  • Are there any known breaking changes we'd want to ship before locking 1.0?
  • Should we do a deprecation pass first (e.g. no_extract, old auth patterns)?
主要语言
Python
星标
716
派生
446
平均合并
8 天 8 小时
30 天内合并 PR
2

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

tableau/server-client-python 的其他 Issue

查看 tableau/server-client-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。