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
分支
444
平均合併
1 天 2 小時
30 天內合併 PR
1

環境準備

從這裡開始

  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 摘要。