Skip to content

Tags: Lumencraft/webstudio

Tags

0.170.0

Toggle 0.170.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix: dropdown menu position on list items (variables list) (webstudio…

…-is#3673)

## Description

1. What is this PR about (link the issue and add a short description)

## Steps for reproduction

1. click button
2. expect xyz

## Code Review

- [ ] hi @kof, I need you to do
  - conceptual review (architecture, feature-correctness)
  - detailed review (read every line)
  - test it on preview

## Before requesting a review

- [ ] made a self-review
- [ ] added inline comments where things may be not obvious (the "why",
not "what")

## Before merging

- [ ] tested locally and on preview environment (preview dev login:
5de6)
- [ ] updated [test
cases](https://github.com/webstudio-is/webstudio/blob/main/apps/builder/docs/test-cases.md)
document
- [ ] added tests
- [ ] if any new env variables are added, added them to `.env` file

hello14c4aad82030ae12f83796d84cb894362d6c67bd

Toggle hello14c4aad82030ae12f83796d84cb894362d6c67bd's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
experimental: fix style preset generation (webstudio-is#3677)

Here fixed style presets generation to reflect new parsed css format.

0.169.0

Toggle 0.169.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix: Static assets redirect to dashboard (webstudio-is#3612)

## Description

1. 404 error instead of redirect on assets.
2. Vercel sets Cache-Control: public, max-age=31536000, immutable for
all /assets/* paths,
even when a 404 error occurs during deployment.
This causes 404 errors on assets to be cached permanently, preventing
updates.
To prevent this, we set "Cache-Control": "public, max-age=0,
must-revalidate" when an asset is not found.


## Steps for reproduction

1. click button
2. expect xyz

## Code Review

- [ ] hi @kof, I need you to do
  - conceptual review (architecture, feature-correctness)
  - detailed review (read every line)
  - test it on preview

## Before requesting a review

- [ ] made a self-review
- [ ] added inline comments where things may be not obvious (the "why",
not "what")

## Before merging

- [ ] tested locally and on preview environment (preview dev login:
5de6)
- [ ] updated [test
cases](https://github.com/webstudio-is/webstudio/blob/main/apps/builder/docs/test-cases.md)
document
- [ ] added tests
- [ ] if any new env variables are added, added them to `.env` file

0.168.0

Toggle 0.168.0's commit message
release

0.167.0

Toggle 0.167.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
build: publish 0.167.0 (webstudio-is#3498)

0.166.2

Toggle 0.166.2's commit message
build: release 28.05.2024

0.166.1

Toggle 0.166.1's commit message
build: release 28.05.2024

0.166.0

Toggle 0.166.0's commit message
build: release 28.05.2024

0.165.0

Toggle 0.165.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
feat: Improve autoplacement when inserting component via 1-click in c…

…omponents panel or via paste (webstudio-is#3422)

Closes webstudio-is#3149

## Description

As a user when I have Heading, Text or similar instances selected which
have a single text node instance, I expect an added component to insert
AFTER such instances.

## Steps for reproduction

1. add heading
2. select heading instance
3. 1-click box
4. see box was added after the heading
5. repeat the same with paste
6. repeat the same with any instance that has only text inside

## Code Review

- [ ] hi @TrySound  , I need you to do
  - conceptual review (architecture, feature-correctness)
  - detailed review (read every line)

- [ ] hi @johnsicili , I need you to do
  - test it on preview

## Before requesting a review

- [ ] made a self-review
- [ ] added inline comments where things may be not obvious (the "why",
not "what")

## Before merging

- [ ] tested locally and on preview environment (preview dev login:
5de6)
- [ ] updated [test
cases](https://github.com/webstudio-is/webstudio/blob/main/apps/builder/docs/test-cases.md)
document
- [ ] added tests
- [ ] if any new env variables are added, added them to `.env.example`
and the `builder/env-check.js` if mandatory

0.164.0

Toggle 0.164.0's commit message
build: Release 20.05.2024 v2