Releases: nocodb/nocodb
0.109.3: Bug Fix Release
π NocoDB : Bug Fix Release
π Closed Issues
- [closed] π Bug: Signup Option still there after deactivating #5976
- [closed] Error on Frontend init (oauth2 client ID) #5971
- [closed] π Bug: 0.109.1 -> 0.109.2 : Migration from 0107004 to 0108002 failed #5957
- [closed] π Bug: Date picker- auto close modal after date is selected #5949
- [closed] π Bug: Impossible to input data to a single select column type in form #5939
- [closed] π Bug: Delete record, undo; links are not re-inserted #5935
What's Changed
- Release 0.109.2 by @github-actions in #5941
- test: add demo table as sub routine by @dstala in #5942
- feat: recover LTAR when undoing delete by @mertmit in #5943
- fix: On selecting day close Datepicker by @pranavxc in #5950
- fix: dynamic batch based on byte size by @mertmit in #5954
- test: pg-meta-db for pw by @dstala in #5937
- test: mysql as root DB for mysql suite by @dstala in #5962
- test/fix: project duplicate suite by @dstala in #5967
- feat: bulk update records using UI by @mertmit in #5928
- fix: LTAR upgrader bug by @pranavxc in #5980
- fix: form view single/multi select behaviour by @pranavxc in #5977
- 0.109.3 Pre-release by @github-actions in #5983
Full Changelog: 0.109.2...0.109.3
0.109.2: Bug Fix Release
π NocoDB : Bug Fix Release
π Closed Issues
- [closed] π Bug: Delete table error #5934
- [closed] π Bug: Error when editing tables with foreign keys #5931
- [Status: Reproducible] π Bug: Single select doesn't work #5926
- [ποΈ Status: In Resolution] π Bug: Not all records returned in row with relations #5906
- [closed] π¦ Feature: sql query as table #5900
What's Changed
- Release 0.109.1 by @github-actions in #5891
- test: project menu role access by @dstala in #5897
- refactor: MetaDB LTAR revamp by @pranavxc in #5874
- fix: revert commit changes made on ncFilterUpgrader_0104004 by @pranavxc in #5911
- New Crowdin updates by @o1lab in #5917
- fix: signOut API by @wingkwong in #5905
- fix: various fixes for UI by @mertmit in #5918
- fix: Form view single/multi select bug by @pranavxc in #5932
- fix: LTAR upgrader bug by @pranavxc in #5933
- fix: Instead of title/alias use id with nested apis to avoid unexpected behaviour by @pranavxc in #5938
- fix: Skip relation delete if it's a virtual relation by @pranavxc in #5936
- 0.109.2 Pre-release by @github-actions in #5940
Full Changelog: 0.109.1...0.109.2
0.109.1: Bug Fix Release
π NocoDB : Bug Fix Release
π Closed Issues
- [π Type: Bug][ποΈ Status: In Resolution] π Bug: projects' Actions missing in dashboard's UI #5883
- [closed] π Bug: Latest Build Failed #5882
- [Status: Reproducible][ποΈ Status: In Resolution] π Bug: Undo after a failed delete operation #5880
- [closed] π Bug: Schema filter not working for SQL Views in database connections #5823
What's Changed
- Release 0.109.0 by @github-actions in #5878
- fix: on delete fail, return error instead of 200 OK by @dstala in #5881
- fix: Filter view list based on current schema in pg and mssql by @pranavxc in #5870
- fix: avoid adding undo if delete fails by @mertmit in #5884
- fix: Show project action icons based project role by @pranavxc in #5885
- fix: save any unsaved data on tab close, view switch, table switch or data reload by @pranavxc in #5867
- 0.109.1 Pre-release by @github-actions in #5890
Full Changelog: 0.109.0...0.109.1
0.109.0
π NocoDB Feature Release : Multiple cell copy paste π
π₯¬ What's new .. What's fresh ?
Multiple cell copy paste
We are happy to add much requested feature of Multiple cell copy & paste
!
π‘Tired of copying and pasting individual cells one by one? We've got great news for you! Introducing the Multiple Cell Copy-Paste feature, designed to enhance your spreadsheet experience. Say goodbye to tedious manual duplication and say hello to effortless efficiency!
π Picture this: with just a few clicks, you can now copy and paste multiple contiguous cells simultaneously. Whether you're duplicating entire columns, or transferring data across different sheets, this powerful feature will save you valuable time and effort.
π NocoDB empowers you with the tools you need to excel in your spreadsheet tasks. Try out the Multiple Cell Copy-Paste feature today and witness the transformation in your productivity!
Screen.Recording.2023-06-12.at.9.04.59.AM.mov.conv.mov
Other updates
Create link between tables by just dragging and dropping tables
The drag-and-drop functionality allows for the seamless creation of LinkToAnotherRecord and Lookup columns, providing a convenient and fast way to establish relations between tables. By simply dragging and dropping tables, users can create link columns, thereby establishing connections between related data sets. The process for creating lookup columns follows a similar procedure, ensuring consistency and ease of use.
Screen.Recording.2023-06-13.at.9.06.44.AM.mov.conv.mov
Join Our Team
Thank you for your love & support
π π
π Closed Issues
- [Status: Reproducible] π Bug: right click context menu options missing #5838
- [Status: Reproducible] UX: Shared view & shared base cursor movements #5829
- [closed] π Bug: Nest 8 error #5815
- [π Type: Bug] Listing API not returning correct result after re-using the table name #5814
- [π£ Priority: Low] π Bug: SQL Error on accessing invalid ROW ID #5812
- [π Scope : Docs] Page not found issue on docs.nocodb.com #5810
- [closed] UX : Delete row related #5803
- [π Type: Bug] π Bug: eyeSlash icon is not shown in form #5798
- [closed] π Bug: duplicate table- scroll into view newly created table on project tree #5795
- [β¨ Type: Enhancement][π£ Priority: Low] π Bug: Add new row button at bottom left of the grid should be sticky #5789
- [closed] π Bug: login username is case sensitive #5787
- [closed] π Bug: Node v19.9.0 #5782
- [ποΈ Status: In Resolution] π Bug: scroll behaviour with partially visible cells #5753
- [β¨ Type: Enhancement] render virtual and normal cells for hm and mm #5660
- [closed] π Bug: Use of lengthy text in form input label & help text #5438
What's Changed
- Release 0.108.1 by @github-actions in #5781
- New Crowdin updates by @o1lab in #5783
- test: filter groups by @dstala in #5785
- fix: Grid view scroll related issues by @pranavxc in #5786
- eyeSlash icon is not shown in form #5798 by @DIWAKARKASHYAP in #5799
- fix: Browser console warnings/errors by @pranavxc in #5797
- fix: After table create/duplicate completion scroll to the new table in treeview by @pranavxc in #5802
- chore(deps): bump @antfu/utils, @windicss/plugin-utils, vite-plugin-windicss, unplugin-icons and unplugin-vue-components in /packages/nc-gui by @dependabot in #5808
- fix(noco-docs): apply NuxtLink on incorrect links by @wingkwong in #5811
- enhancement: hm / mm cells by @wingkwong in #5724
- chore(deps): bump vite from 2.9.15 to 2.9.16 in /packages/nc-gui by @dependabot in #5820
- Bug fix for issue #5438, resolved text-overflow with text-wrapping by @nith2001 in #5531
- revise: grid context menu by @mertmit in #5813
- Configure Renovate by @renovate in #5822
- fix: Clear alias cache when renaming table/view by @pranavxc in #5832
- fix: Project user mapping cleanup during project delete by @dstala in #5835
- fix: Read api - if record is missing return null by @pranavxc in #5833
- fix: make cell selectable and skip paste behaviour if not permitted by @pranavxc in #5842
- fix: avoid clearing selected range on expand by @mertmit in #5839
- enhancement: sticky add new row by @pranavxc in #5805
- feat: add install:local-sdk by @wingkwong in #5845
- feat: Drag n drop LTAR and Lookup creation by @pranavxc in #5807
- Update index.js by @WALL-E in #5856
- test: use meta-db project for non-sakila db by @dstala in #5863
- feat: render new lines for LongText by @mertmit in #5849
- fix: Make username case insensitive by @pranavxc in #5868
- Remove delete confirm dialog by @pranavxc in #5869
- refactor: MetaDB LTAR revamp by @pranavxc in #5816
- Revert "refactor: MetaDB LTAR revamp" by @pranavxc in #5873
- feat: multiple paste by @mertmit in #5847
- 0.109.0 Pre-release by @github-actions in #5877
New Contributors
- @DIWAKARKASHYAP made their first contribution in #5799
- @WALL-E made their first contribution in #5856
Full Changelog: 0.108.1...0.109.0
0.108.1: Bug Fix Release
π NocoDB : Bug Fix Release
π Closed Issues
- [closed] π Bug: Crash with 0.108.0 when NC_PUBLIC_URL is set #5778
- [Status: Reproducible] π Bug: Can't re-size columns in shared view #5772
- [closed] π¦ Feature: Remove initial boolean operator when adding first Filter (Group) in Filtering UI #5648
What's Changed
- Release 0.108.0 by @github-actions in #5775
- fix: Allow changing column width in shared grid view by @pranavxc in #5776
- fix: remove envs props from config which is no longer in use by @pranavxc in #5779
- 0.108.1 Pre-release by @github-actions in #5780
Full Changelog: 0.108.0...0.108.1
0.108.0
π NocoDB Feature Release : Standardising DateTime Fields & Worker Node π
- Please use the following discussion thread for discussing about the release
π₯¬ What's new .. What's fresh ?
We are excited to introduce a new feature that manages to provide a simple and intuitive way to handle get/set of Datetime (with or without timezone) fields across all databases. NocoDB does this by simply expecting UTC in and out of the APIs like below.
Fields | API Input | API Output |
---|---|---|
Datetime | UTC | UTC |
Datetime (with timezone) | UTC | UTC |
Though at the surface it is very simple and intuitive way to manage datetime fields there has been significant work behind this release. This release brings consistency and improved accuracy to time-related operations, ensuring a smoother user experience across different timezones.
Key Highlights:
-
Conversion to UTC: All DateTime fields without timezone will now be stored in UTC format within database. This change guarantees uniformity and facilitates standardized handling of time across the application.
-
API Request/Response: DateTime values will be sent/received in UTC only. This enables easier integration with external systems and enhances interoperability with various Databases that have their own timezone.
-
NocoDB User Interface (UI): To provide a more intuitive experience, DateTime values displayed within the NocoDB UI will be just user's local (browser) timezone. This ensures that users see DateTime information in a familiar and easily understandable format.
-
Correct Creation Time in Audit Log: With this update, the creation time in the Audit Log will be accurately reflected in your local timezone. Behind the scene it is stored in UTC. This enhancement ensures that all logged actions are recorded with the correct timestamp, maintaining consistency throughout the system.
We believe this enhancement will greatly improve the consistency and accuracy of DateTime values within our application. We aim to streamline time-related operations and facilitate a more cohesive user experience.
π¨ Breaking changes π¨
Any datetime related field is now in UTC format in its API input and output. This will be a breaking change.
Please note the following details regarding this breaking change:
- No Upgrader Available: With this release, there will NOT be a data upgrader provided to automatically convert existing DateTime (without timezone) fields to user's Database/Server time. The responsibility of updating DateTime fields will fall on the users and database administrators of the application. So if your application relies on DateTime values (without timezone) and you are upgrading to this new release, it will be necessary to manually convert values to UTC.
We understand that this breaking change may require additional effort and planning on your part. However, this decision was made to ensure a more consistent and accurate handling of DateTime values moving forward. We apologize for any inconvenience this and recommend reaching out to our team members in Discord (@wingkwong (#3278
) @dstala (#4285
)) for guidance and assistance with the manual conversion process.
Worker Node
We are thrilled to announce the introduction of a new feature that allows users to create worker instances in NocoDB. A worker instance is a specialized NocoDB instance designed specifically for job processing, without port binding and controllers. This update empowers users to offload and efficiently process jobs from a dedicated worker environment, enhancing the overall performance and scalability of their applications.
Key Features:
-
Worker Instance Creation: Users can now create worker instances by utilizing a new environment variable. By setting the
NC_WORKER_CONTAINER
environment value as true, the instance will be configured as a worker, solely responsible for listening to and processing jobs from the jobs queue. -
Job Processing Efficiency: With the introduction of worker instances, users can significantly improve job processing efficiency. By separating job processing from the primary instance, the worker environment focuses exclusively on handling and executing jobs, resulting in enhanced performance and resource allocation.
-
Redis Integration: To utilize worker instances effectively, both the primary instance and the worker instance need to utilize Redis for job queue management. Users need to provide the Redis URL (
NC_REDIS_URL
) as part of the configuration, ensuring seamless coordination between the primary and worker instances.
We believe this feature will greatly benefit users seeking to optimize job processing in their applications. By leveraging dedicated worker instances, users can achieve better performance, scalability, and resource allocation. It is important to note that the worker instance operates independently of the primary instance, allowing for more efficient and streamlined job processing.
Join Our Team
Thank you for your love & support
π π
What's Changed
- Revert "Revert "refactor: timezone"" by @wingkwong in #5684
- fix: datetime followup by @wingkwong in #5678
- Release 0.107.5 by @github-actions in #5750
- refactor: timezone locale by @wingkwong in #5689
- feat: worker container by @mertmit in #5711
- New Crowdin updates by @o1lab in #5751
- New Crowdin updates by @o1lab in #5752
- 0.108.0-beta.0 Pre-release by @github-actions in #5754
- Release 0.108.0-beta.0 by @github-actions in #5755
- test: local tz fix for browser in non-UTC by @dstala in #5759
- fix: Set fallback dashboard path while creating config by @pranavxc in #5762
- fix: filter groups by @wingkwong in #5771
- fix(nocodb): Fixed filtering boolean visual bug by @nith2001 in #5705
- fix: include lookup related metas in shared view meta api by @pranavxc in #5767
- fix: revoked user permission by @wingkwong in #5770
- fix: set refresh-token on login and correction in refresh-token based api by @pranavxc in #5764
- refactor: lint by @wingkwong in #5773
- 0.108.0 Pre-release by @github-actions in #5774
New Contributors
Full Changelog: 0.107.5...0.108.0
- [Status: Reproducible] π Bug: Use of filter groups throws error #5769
- [closed] π Bug: API Query Param Not Working After Update #5768
- [closed] π Bug: Shared view redirects to sign-in page #5766
- [π Type: Bug] π Bug: User revoked from project is able to change the project name #5763
- [closed] π¦ Feature: Specific Roles to Access to specific tables #5692
0.108.0-beta.0
π NocoDB Feature Beta Release : Standardising DateTime Fields & Worker Node π
- Please use the following discussion thread for discussing about the release
π₯¬ What's new .. What's fresh ?
We are excited to introduce a new feature that manages to provide a simple and intuitive way to handle get/set of Datetime (with or without timezone) fields across all databases. NocoDB does this by simply expecting UTC in and out of the APIs like below.
Fields | API Input | API Output |
---|---|---|
Datetime | UTC | UTC |
Datetime (with timezone) | UTC | UTC |
Though at the surface it is very simple and intuitive way to manage datetime fields there has been significant work behind this release. This release brings consistency and improved accuracy to time-related operations, ensuring a smoother user experience across different timezones.
Key Highlights:
-
Conversion to UTC: All DateTime fields without timezone will now be stored in UTC format within database. This change guarantees uniformity and facilitates standardized handling of time across the application.
-
API Request/Response: DateTime values will be sent/received in UTC only. This enables easier integration with external systems and enhances interoperability with various Databases that have their own timezone.
-
NocoDB User Interface (UI): To provide a more intuitive experience, DateTime values displayed within the NocoDB UI will be just user's local (browser) timezone. This ensures that users see DateTime information in a familiar and easily understandable format.
-
Correct Creation Time in Audit Log: With this update, the creation time in the Audit Log will be accurately reflected in your local timezone. Behind the scene it is stored in UTC. This enhancement ensures that all logged actions are recorded with the correct timestamp, maintaining consistency throughout the system.
We believe this enhancement will greatly improve the consistency and accuracy of DateTime values within our application. We aim to streamline time-related operations and facilitate a more cohesive user experience.
π¨ Breaking changes π¨
Any datetime related field is now in UTC format in its API input and output. This will be a breaking change.
Please note the following details regarding this breaking change:
- No Upgrader Available: With this release, there will NOT be a data upgrader provided to automatically convert existing DateTime (without timezone) fields to user's Database/Server time. The responsibility of updating DateTime fields will fall on the users and database administrators of the application. So if your application relies on DateTime values (without timezone) and you are upgrading to this new release, it will be necessary to manually convert values to UTC.
We understand that this breaking change may require additional effort and planning on your part. However, this decision was made to ensure a more consistent and accurate handling of DateTime values moving forward. We apologize for any inconvenience this and recommend reaching out to our team members in Discord (@wingkwong (#3278
) @dstala (#4285
)) for guidance and assistance with the manual conversion process.
Worker Node
We are thrilled to announce the introduction of a new feature that allows users to create worker instances in NocoDB. A worker instance is a specialized NocoDB instance designed specifically for job processing, without port binding and controllers. This update empowers users to offload and efficiently process jobs from a dedicated worker environment, enhancing the overall performance and scalability of their applications.
Key Features:
-
Worker Instance Creation: Users can now create worker instances by utilizing a new environment variable. By setting the
NC_WORKER_CONTAINER
environment value as true, the instance will be configured as a worker, solely responsible for listening to and processing jobs from the jobs queue. -
Job Processing Efficiency: With the introduction of worker instances, users can significantly improve job processing efficiency. By separating job processing from the primary instance, the worker environment focuses exclusively on handling and executing jobs, resulting in enhanced performance and resource allocation.
-
Redis Integration: To utilize worker instances effectively, both the primary instance and the worker instance need to utilize Redis for job queue management. Users need to provide the Redis URL (
NC_REDIS_URL
) as part of the configuration, ensuring seamless coordination between the primary and worker instances.
We believe this feature will greatly benefit users seeking to optimize job processing in their applications. By leveraging dedicated worker instances, users can achieve better performance, scalability, and resource allocation. It is important to note that the worker instance operates independently of the primary instance, allowing for more efficient and streamlined job processing.
Join Our Team
Thank you for your love & support
π π
What's Changed
- Revert "Revert "refactor: timezone"" by @wingkwong in #5684
- fix: datetime followup by @wingkwong in #5678
- Release 0.107.5 by @github-actions in #5750
- refactor: timezone locale by @wingkwong in #5689
- feat: worker container by @mertmit in #5711
- New Crowdin updates by @o1lab in #5751
- New Crowdin updates by @o1lab in #5752
- 0.108.0-beta.0 Pre-release by @github-actions in #5754
Full Changelog: 0.107.5...0.108.0-beta.0
0.107.5: Bug Fix Release
π NocoDB : Bug Fix Release
π Closed Issues
- [closed] π Bug: Form view not rendering available options #5740
- [closed] π Bug: Uncaught ReferenceError: SwaggerUIBundle is not defined #5739
What's Changed
- Release 0.107.4 by @github-actions in #5728
- fix: rollback transaction if bulk insert errors by @dstala in #5743
- Fix: Read data API - allow nested fields query param by @pranavxc in #5735
- fix: drop dtxp max length from column request schema by @mertmit in #5730
- New Crowdin updates by @o1lab in #5746
- 0.107.5 Pre-release by @github-actions in #5749
Full Changelog: 0.107.4...0.107.5
0.107.4: Bug Fix Release
π NocoDB : Bug Fix Release
π Closed Issues
- [π Type: Bug] π Bug: Super Admin No longer created during initialization #5722
- [π Type: Bug] Storage upload unauthorized using xc-token authentication header(it works with xc-auth) #5713
- [closed] π¦ Feature: Select number of row to display in each page #5708
- [π Type: Bug] π Bug: Metadata not in sync and breaking most of the features #5701
- [π Type: Bug] π Bug: model list cache ignores base_id #5568
What's Changed
- Release 0.107.3 by @github-actions in #5700
- fix(nocodb): model list cache by @wingkwong in #5707
- chore(deps): bump socket.io-parser from 4.2.2 to 4.2.3 in /packages/nocodb by @dependabot in #5717
- chore(deps): bump socket.io-parser from 4.2.1 to 4.2.3 in /packages/nc-gui by @dependabot in #5716
- fix: Update project base config encryption with proper secret key by @pranavxc in #5718
- fix(nocodb): assign dbuser id n roles to user by @wingkwong in #5720
- fix(nocodb): incorrect public path for docker by @wingkwong in #5721
- fix: load super admin user from env if env is set by @pranavxc in #5723
- 0.107.4 Pre-release by @github-actions in #5727
Full Changelog: 0.107.3...0.107.4
0.107.3: Bug Fix Release
π NocoDB : Bug Fix Release
π Closed Issues
- [π Type: Bug] π Bug: LinkToAnotherRecord dosen't work in Shared View Forms #5694
- [β¨ Type: Enhancement] π¦ Enhancement: Formula functions prefer to be case-insensitive #5640
What's Changed
- Release 0.107.2 by @github-actions in #5696
- fix(nc-gui): incorrect shared form logic by @wingkwong in #5697
- chore: clean up image build script and bug fix with packaging by @starbirdtech383 in #5698
- enhancement: case insensitive formula by @wingkwong in #5682
- 0.107.3 Pre-release by @github-actions in #5699
Full Changelog: 0.107.2...0.107.3