Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency @tinacms/cli to v1 #125

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 2, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@tinacms/cli ^0.60.0 -> ^1.0.0 age adoption passing confidence

Release Notes

tinacms/tinacms

v1.5.14

Compare Source

Patch Changes

v1.5.13

Compare Source

Patch Changes
  • 5a60189: Add support for "quick editing". By adding the [data-tina-field] attribute to your elements, editors can click to see the
    correct form and field focused in the sidebar.

    This work closely resembles the "Active Feild Indicator" feature.
    Which will be phased in out place of this in the future. Note that the attribute name is different, [data-tinafield] is the value
    for the "Active Field Indicator" while [data-tina-field] is the new attribute.

    The tinaField helper function should now only be used with the [data-tina-field] attibute.

    Adds experimental support for Vercel previews, the useVisualEditing hook from @tinacms/vercel-previews can be used
    to activate edit mode and listen for Vercel edit events.

  • Updated dependencies [ca74add]

  • Updated dependencies [0f5557d]

  • Updated dependencies [ff4c1e0]

  • Updated dependencies [6fefa56]

  • Updated dependencies [7f95c1c]

v1.5.12

Compare Source

Patch Changes

v1.5.11

Compare Source

Patch Changes

v1.5.10

Compare Source

Patch Changes

v1.5.9

Compare Source

Patch Changes

v1.5.8

Compare Source

Patch Changes
  • 5cb7305: fix issue where migration would error if a user selected no to migrating templates
  • 012ed53: Fix regression where build.host was not passed correctly
  • Updated dependencies [eba7e5e]

v1.5.7

Compare Source

Patch Changes

v1.5.6

Compare Source

Patch Changes

v1.5.5

Compare Source

Patch Changes

v1.5.4

Compare Source

Patch Changes

v1.5.3

Compare Source

Patch Changes

v1.5.2

Compare Source

Patch Changes

v1.5.1

Compare Source

Patch Changes

v1.5.0

Compare Source

Minor Changes
  • bbae12b: Changes Tailwind config to also search for class names within user's config and related custom components
Patch Changes

v1.4.1

Compare Source

v1.4.0

Compare Source

Minor Changes
  • 76c984b: Use new API endpoint in content api reqests
  • 202cd71: Internal updates to the CLI
Patch Changes

v1.3.3

Compare Source

Patch Changes

v1.3.2

Compare Source

Patch Changes

v1.3.1

Compare Source

Patch Changes
  • 591c6e9: Wait for DB before checking schema.

v1.3.0

Compare Source

Minor Changes
  • d9962ed: rm previewSrc from images
Patch Changes

v1.2.2

Compare Source

Patch Changes

v1.2.1

Compare Source

Patch Changes

v1.2.0

Compare Source

Minor Changes
  • 1691474: When markdown files fail to parse, fallback to the non-MDX parser
Patch Changes

v1.1.0

Compare Source

Minor Changes
  • efd56e7: Replace Store with AbstractLevel in Database. Update CLI to allow user to configure Database.
Patch Changes

v1.0.9

Compare Source

Patch Changes

v1.0.8

Compare Source

Patch Changes

v1.0.7

Compare Source

Patch Changes
  • 849dc0b: Adds more features to the forestry migration tool

  • 23942cf: Add support for --rootPath argument in CLI commands

  • e7c404b: Support remote path configuration for separate content repos

    Tina now supports serving content from a separate Git repo.

Local development workflow

To enable this during local development, point
this config at the root of the content repo.

NOTE: Relative paths are fine to use here, but make sure it's relative to the .tina/config file

localContentPath: process.env.REMOTE_ROOT_PATH // eg. '../../my-content-repo'
Production workflow

For production, your config should use the clientId, branch, and token values that are associated with your content repo.

v1.0.6

Compare Source

Patch Changes

v1.0.5

Compare Source

Patch Changes

v1.0.4

Compare Source

Patch Changes

v1.0.3

Compare Source

Patch Changes

v1.0.2

Compare Source

Patch Changes

v1.0.1

Compare Source

Patch Changes

v1.0.0

Compare Source

Major Changes
Patch Changes

v0.62.3

Compare Source

Patch Changes

v0.62.2

Compare Source

Patch Changes

v0.62.1

Compare Source

Patch Changes

v0.62.0

Compare Source

Minor Changes
  • 0fb26ac: Updated to use new init for iframe way of editing.
Patch Changes

v0.61.27

Compare Source

Patch Changes

v0.61.26

Compare Source

Patch Changes

v0.61.25

Compare Source

Patch Changes

v0.61.24

Compare Source

Patch Changes

v0.61.23

Compare Source

Patch Changes

v0.61.22

Compare Source

Patch Changes

v0.61.21

Compare Source

Patch Changes

v0.61.20

Compare Source

Patch Changes

v0.61.19

Compare Source

Patch Changes

v0.61.18

Compare Source

Patch Changes

v0.61.17

Compare Source

Patch Changes

v0.61.16

Compare Source

Patch Changes

v0.61.15

Compare Source

Patch Changes

v0.61.14

Compare Source

Patch Changes

v0.61.13

Compare Source

Patch Changes
  • 9183157: This allows us to use a leaner define function for the standalone config. Right now we're balancing a lot on the defineSchema/defineConfig types and have a few overlapping things like client, which accepts both an optional object with referenceDepth config as well as the autogenerated http client.

    One thing it does that's a bit different is it uses the apiUrl from the client generation function and sends it through as a global constant to the Vite app, this avoids the need for the generated client.

  • 4adf126: Add support for experimental iframe mode

  • Updated dependencies [9183157]

  • Updated dependencies [4adf126]

  • Updated dependencies [f8b8937]

v0.61.12

Compare Source

Patch Changes

v0.61.11

Compare Source

Patch Changes

v0.61.10

Compare Source

Patch Changes

[`v0.


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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented May 2, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
next-saas-starter ❌ Failed (Inspect) May 31, 2023 8:53pm

@renovate
Copy link
Contributor Author

renovate bot commented Jun 12, 2023

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 1.x releases. But if you manually upgrade to 1.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/tinacms-cli-1.x branch June 12, 2023 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant