Update dependency nocodb to ^0.301.0 - autoclosed#184
Closed
renovate[bot] wants to merge 1 commit intodevelopfrom
Closed
Update dependency nocodb to ^0.301.0 - autoclosed#184renovate[bot] wants to merge 1 commit intodevelopfrom
renovate[bot] wants to merge 1 commit intodevelopfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.83.0→^0.301.0Release Notes
nocodb/nocodb (nocodb)
v0.301.3: : Bug Fix ReleaseCompare Source
🐛 Closed Issues
queryRecordstool in the MCP service regarding time is unclear, causing the LLM to be unable to correctly query time-related filter conditions #12944What's Changed
20260201536 by @dstala in #1301620260121845 by @dstala in #13035Security fixes
This release addresses multiple security vulnerabilities. Full details will be published via GitHub Security Advisories after users have had time to upgrade.
Acknowledgements
We thank the following researchers for responsibly reporting these vulnerabilities:
New Contributors
Full Changelog: nocodb/nocodb@0.301.2...0.301.3
v0.301.2: : Bug Fix ReleaseCompare Source
🐛 Closed Issues
What's Changed
Full Changelog: nocodb/nocodb@0.301.1...0.301.2
v0.301.1: : Bug Fix ReleaseCompare Source
🐛 Closed Issues
What's Changed
Full Changelog: nocodb/nocodb@0.301.0...0.301.1
v0.301.0: : Darkmode, Custom Webhook Payload & Groupby AggregationsCompare Source
🌗 Dark Mode Is Here - Hooooooooooooray!!!!!!!!
Dark Mode has officially landed in NocoDB Community Edition. Sleeker, easier on the eyes, and built for long sessions—whether you’re shipping late at night or just love a modern dark UI. Every grid, form, and workflow now looks sharper and feels better, without changing how you work. Learn more
🔗 Webhook Payload Customisation ( 🔑 Unlocked from enterprise edition )
Total control, now unlocked. Webhook Custom Payloads are no longer Cloud-only—this powerful capability is now available in NocoDB Community Edition. Shape your webhook requests exactly the way your integrations need them. Cleaner payloads, smarter automations, and seamless connections with any external system. Learn more
📊 Grid View Group-by Aggregations ( 🔑 Unlocked from enterprise edition )
Data insights just leveled up. Group-by Aggregations are now open in NocoDB Community Edition, bringing Cloud-grade analytics straight into your views. Instantly roll up counts, totals, averages, and more—right inside grouped data. No exports. No extra tools. Just answers, instantly. Learn more
🛠️ Other Updates
Default view was locked to Grid: Tables always opened in Grid view, even when another view was more relevant. You can now set any view as the default for a table, ensuring users land directly on the most meaningful view.
Commenters and viewers had full toolbar access: Limited-access roles were exposed to advanced actions. Commenter and Viewer roles now work in a simplified interface without toolbar access, keeping the experience focused, secure, and role-appropriate.
Addressed several bug fixes and improved security.
📢 License Update
Starting with this release, NocoDB is transitioning its license from AGPL 3.0 to a Fair-code–based Sustainable Use License. This change is designed to protect the long-term sustainability of the project while keeping NocoDB open, transparent, and community-driven. The Fair-code model has resonated strongly across the open-source and no-code communities, with projects adopting this approach now collectively representing over 170,000+ GitHub stars : a signal that sustainable open-source business models are not just viable, but thriving. The new license continues to allow free use, modification, and self-hosting, while placing reasonable limits on commercial offerings.
👉 View the full license terms here
This step helps ensure that innovation in NocoDB is funded, maintained, and driven by the community for the long run.
Using base names and table names in API endpoints is no longer supported.
All API integrations must now use IDs instead of names.
Including names as part of API paths is highly discouraged, as names can be changed by other users, which may break existing integrations unexpectedly.
Before
http://localhost:8081/api/v1/db/data/noco/Getting%20Started/Table-1After
http://localhost:8081/api/v1/db/data/noco/pjq0r488d4gt2xz/mtan85lkqcvf8i7Bug fixes
branch duringpnpm bootstrap`` #12586v0.300.0Compare Source
v0.265.1: : Bug Fix ReleaseCompare Source
🐛 Closed Issues
What's Changed
New Contributors
Full Changelog: nocodb/nocodb@0.265.0...0.265.1
v0.265.0: : Introducing MCP ServerCompare Source
🚀 NocoDB : Feature Release
MCP Server – Talk to your database through AI
No more endless clicks or filters. With MCP Server, your NocoDB workspace connects directly to AI-powered tools like Claude, Cursor, and Windsurf. Just ask in plain language, and your database answers back.
What’s Changed?
This is just the beginning—MCP opens the door for even deeper AI + database workflows coming soon.
👉 Get started with MCP integration →
Other Updates
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.