steipete

#!/usr/bin/env bun
"use strict";

const fs = require("fs");
const { execSync } = require("child_process");
const path = require("path");

// ANSI color constants
const c = {
  cy: '\033[36m',  // cyan

JohnAdamsy

Identity

You are an expert AI assistant integrated into the Cursor IDE. Your current specialty is Plan Mode. Your sole purpose in this mode is to collaborate with developers to transform a high-level feature idea into a comprehensive and actionable software plan.

You guide the user through a structured process of defining requirements, creating a technical design, and generating a detailed list of implementation tasks. You are a methodical planner and architect.

You are managed by an autonomous process which takes your output, performs the actions you requested, and is supervised by a human user.

You talk like a human, not like a bot. You reflect the user's input style in your responses.

Rules

mberman84

- After making changes, ALWAYS make sure to start up a new server so I can test it.
- Always look for existing code to iterate on instead of creating new code.
- Do not drastically change the patterns before trying to iterate on existing patterns.
- Always kill all existing related servers that may have been created in previous testing before trying to start a new server.
- Always prefer simple solutions
- Avoid duplication of code whenever possible, which means checking for other areas of the codebase that might already have similar code and functionality
- Write code that takes into account the different environments: dev, test, and prod
- You are careful to only make changes that are requested or you are confident are well understood and related to the change being requested
- When fixing an issue or bug, do not introduce a new pattern or technology without first exhausting all options for the existing implementation. And if you finally do this, make sure to remove the old implementation afterwards so we d

0xernesto

Semantic Release bot flow (signed/verified commits)

Overview

This semantic-release publishing flow consists of using a bot for publishing releases with signed/verified commits. This setup requires creating a Github App, a user account for the bot to use, and adding the following Github Actions secrets to the repo it is being used in:

• NPM_TOKEN
  • Refer to “Generating an NPM token” section.
• MY_RELEASER_USER_EMAIL
• Refer to the “Create a new Github user account for the bot” section

0xernesto

Semantic Release bot flow

Overview

This semantic-release publishing flow consists of using a bot for publishing releases. Note that commits by this bot will not be signed/verfied. If this is a requirement for you, refer to this guide. This setup requires creating a Github App and adding the following Github Actions secrets to the repo it is being used in:

• NPM_TOKEN
  • Refer to “Generating an NPM token” section.
• MY_RELEASER_ID
• Refer to “Creating a GitHub App” section

chase2981

import * as React from "react";
import {
    Manager, Actions, MessagingCanvas, MessagingCanvasContext, DynamicComponent, ContextProvider, MessageList, StateHelper, TaskHelper, ITask,
    Supervisor,
    TaskChannelDefinition,
    TaskContextProps,
    Theme
} from '@twilio/flex-ui';
import CoreApiService from '../Shared/CoreApiService';
import { Channel } from 'twilio-chat/lib/channel';

sandfox

phases:
  install:
    commands:
      - . codebuild_nvm_wrapper.sh
      - npm install
      - node -v

soulmachine

First of all, please note that token expiration and revoking are two different things.

1. Expiration only happens for web apps, not for native mobile apps, because native apps never expire.
2. Revoking only happens when (1) uses click the logout button on the website or native Apps;(2) users reset their passwords; (3) users revoke their tokens explicitly in the administration panel.

1. How to hadle JWT expiration

A JWT token that never expires is dangerous if the token is stolen then someone can always access the user's data.

Quoted from JWT RFC:

joshdholtz

STUFF = this is some stuff

mohsin

1. Add to project-level build.gradle:

allprojects {
    ...
    afterEvaluate { project ->
        def propsFile = rootProject.file('keystore.properties')
        def configName = 'release'

        if (propsFile.exists() && project.hasProperty("android") && project.android.signingConfigs.hasProperty(configName)) {