Provider produced inconsistent result after apply updating project

[dokterbob]

module.sentry.sentry_project.project: Modifying... [id=bogus_id_1]
╷
│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to module.sentry.sentry_project.project, provider "provider[\"registry.terraform.io/jianyuan/sentry\"]" produced an unexpected new value: .id: was
│ cty.StringVal("bogus_id_1"), but now cty.StringVal("other_id").
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Provider version: 0.14.3

[doctorperceptron]

Same issue with the javascript_loader_script field:

│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to module.blog_server_sentry.sentry_key.project_key, provider |"module.blog_server_sentry.provider[\"registry.terraform.io/jianyuan/sentry\"]" produced an unexpected new value:
│ .javascript_loader_script.performance_monitoring_enabled: was cty.False, but now cty.True.
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to module.blog_server_sentry.sentry_key.project_key, provider |"module.blog_server_sentry.provider[\"registry.terraform.io/jianyuan/sentry\"]" produced an unexpected new value:
│ .javascript_loader_script.session_replay_enabled: was cty.False, but now cty.True.
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Provider version v0.14.3

Is this a known bug with this version?

[nyadav810]

+1, seeing this for sentry_issue_alert.actions_v2.notify_email.fallthrough_type as well.

Provider version 0.14.4

│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to
│ module.sentry[0].sentry_issue_alert.dash_errors_volume, provider
│ "provider[\"registry.terraform.io/jianyuan/sentry\"]" produced an
│ unexpected new value: .actions_v2[1].notify_email.fallthrough_type: was
│ cty.StringVal("AllMembers"), but now null.
│ 
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.