Skip to content

Add enhancement proposal process#12248

Merged
sfc-gh-jrieke merged 19 commits intodevelopfrom
add-step-process
Nov 13, 2025
Merged

Add enhancement proposal process#12248
sfc-gh-jrieke merged 19 commits intodevelopfrom
add-step-process

Conversation

@lukasmasuch
Copy link
Copy Markdown
Collaborator

@lukasmasuch lukasmasuch commented Aug 16, 2025

Describe your changes

Adds lightweight process that allows anyone to contribute and discuss enhancement proposals for Streamlit.


Contribution License Agreement

By submitting this pull request you agree that all contributions to this project are made under the Apache 2.0 license.

@snyk-io
Copy link
Copy Markdown
Contributor

snyk-io bot commented Aug 16, 2025

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Licenses 0 0 0 0 0 issues
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Aug 16, 2025

✅ PR preview is ready!

Name Link
📦 Wheel file https://core-previews.s3-us-west-2.amazonaws.com/pr-12248/streamlit-1.51.0-py3-none-any.whl
📦 @streamlit/component-v2-lib Download from artifacts
🕹️ Preview app pr-12248.streamlit.app (☁️ Deploy here if not accessible)

@lukasmasuch lukasmasuch added security-assessment-completed change:other PR contains other type of change impact:users PR changes affect end users labels Aug 21, 2025
@lukasmasuch lukasmasuch requested a review from jrieke August 21, 2025 09:28
@lukasmasuch lukasmasuch changed the title [WIP] Add enhancement proposal process Add enhancement proposal process Aug 21, 2025
@lukasmasuch lukasmasuch marked this pull request as ready for review August 21, 2025 09:29
@lukasmasuch lukasmasuch requested a review from a team as a code owner September 3, 2025 20:34
@sfc-gh-jrieke sfc-gh-jrieke enabled auto-merge (squash) November 13, 2025 01:14
Check the boxes or add a comment with the reason it cannot be checked.
-->

- [ ] Works on all deployment platforms (e.g. [Streamlit Community Cloud](https://streamlit.io/cloud), [Streamlit in Snowflake](https://www.snowflake.com/en/product/features/streamlit-in-snowflake/), [Hugging Face Spaces](https://huggingface.co/spaces))?
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question/nit: Do you mean, "should this work on all platforms?" or "will this work on all platforms?" When I read this, it sounds to me like it's already built and should work on all deployment platforms.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The question is about checking it we can come up with reasons at speccing time why this might be problematic on a specific platform. So it's more about "will this work on all platforms". I can also clarify this slightly more.

Comment thread specs/README.md
- Keep the PR in Draft until it’s ready for discussion
4. When ready, mark the PR "Ready for review" on GitHub. All discussion on the spec
should happen on the PR.
5. Merging requires at least two approvals from core maintainers.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: What is the significance of merging a spec? Does this mean it's ready to be worked on? Can specs be merged in status: draft?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think for now we only plan to merge approved/ready specs. Specs in draft are just open PRs. I can clarify this a bit more

Copy link
Copy Markdown
Contributor

@sfc-gh-nbellante sfc-gh-nbellante left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple q's but otherwise LGTM!

@sfc-gh-jrieke sfc-gh-jrieke merged commit 2f757e6 into develop Nov 13, 2025
39 checks passed
@sfc-gh-jrieke sfc-gh-jrieke deleted the add-step-process branch November 13, 2025 22:15
@lukasmasuch
Copy link
Copy Markdown
Collaborator Author

@sfc-gh-nbellante sorry, PR was on auto-merge. I will address the comments in a follow up

@sfc-gh-nbellante
Copy link
Copy Markdown
Contributor

@sfc-gh-nbellante sorry, PR was on auto-merge. I will address the comments in a follow up

👌

@lukasmasuch lukasmasuch mentioned this pull request Nov 17, 2025
lukasmasuch added a commit that referenced this pull request Nov 19, 2025
## Describe your changes

Applies some feedback from
#12248 which couldn't be
incorporated since the PR was set to auto-merge.

---

**Contribution License Agreement**

By submitting this pull request you agree that all contributions to this
project are made under the Apache 2.0 license.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

change:other PR contains other type of change impact:users PR changes affect end users

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants